On Tue, Mar 15, 2022 at 10:33:42AM -0400, Jan Wieck wrote:
> Also, the CSV format, while human readable to a degree, wasn't meant for
> direct, human consumption. It was meant to be read by programs and at the
> time, CSV made the most sense.
FWIW, I have noticed that this patch was still listed i
On 3/15/22 10:12, Andrew Dunstan wrote:
On 3/15/22 09:30, hubert depesz lubaczewski wrote:
On Tue, Mar 15, 2022 at 09:31:19AM +0800, lupeng wrote:
Dear Hackers
When I audit the Postgresql database recently, I found that after
configuring the log type as csv, the output log content is as follow
On 3/15/22 09:30, hubert depesz lubaczewski wrote:
> On Tue, Mar 15, 2022 at 09:31:19AM +0800, lupeng wrote:
>> Dear Hackers
>> When I audit the Postgresql database recently, I found that after
>> configuring the log type as csv, the output log content is as follows:
>> "database ""lp_db1"" does
On Tue, Mar 15, 2022 at 09:31:19AM +0800, lupeng wrote:
> Dear Hackers
> When I audit the Postgresql database recently, I found that after
> configuring the log type as csv, the output log content is as follows:
> "database ""lp_db1"" does not exist","DROP DATABASE
> lp_db1;",,"dropdb, dbcomman
Hi,
On Tue, Mar 15, 2022 at 09:31:19AM +0800, lupeng wrote:
>
> When I audit the Postgresql database recently, I found that after configuring
> the log type as csv, the output log content is as follows: "database
> ""lp_db1"" does not exist","DROP DATABASE lp_db1;",,"dropdb,
> dbcommands.c:841
Dear Hackers
When I audit the Postgresql database recently, I found that after configuring
the log type as csv, the output log content is as follows: "database ""lp_db1""
does not exist","DROP DATABASE lp_db1;",,"dropdb,
dbcommands.c:841","","client backend",,0 It is ve
