Re: [BUG] temporary file usage report with extended protocol and unnamed portals - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: [BUG] temporary file usage report with extended protocol and unnamed portals
Date
Msg-id CAA5RZ0veipJ8HVn8XeiViYOLhQMU74UJFe7c6DUiZ5B2sokf6A@mail.gmail.com
Whole thread Raw
In response to Re: [BUG] temporary file usage report with extended protocol and unnamed portals  (Mircea Cadariu <cadariu.mircea@gmail.com>)
Responses Re: [BUG] temporary file usage report with extended protocol and unnamed portals
List pgsql-hackers
> One argument for keeping the tests would be that they nicely bring together the side-effect (logging) and these
use-cases,whereas in the code they're pretty distant, making the connection not obvious.
 

Another argument is that we have no coverage on temp logging, which
is why this bug was discovered. There are likely plenty of tools
out there, for example pgbadger or manual log analysis, that
have probably misinterpreted temporary usage all this time,
because of the way the data was emitted.

--
Sami



pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: pg_stat_statements: faster search by queryid
Next
From: vignesh C
Date:
Subject: Re: Logical Replication of sequences