Robert Treat <[EMAIL PROTECTED]> writes:
> I think better would be a GUC "log_to_table" which wrote all standard
> out/err to a pg_log table. of course, I doubt you could make this
> foolproof (how to log startup errors in this table?) but it could be a
> start.
How would a failed transaction make any entries in such a table? How
would you handle maintenance operations on the table that require
exclusive lock? (vacuum full, reindex, etc)
It seems possible that you could make this work if you piped stderr to a
buffering process that was itself a database client, and issued INSERTs
to put the rows into the table, and could buffer pending data whenever
someone else had the table locked (eg for vacuum). I'd not care to try
to get backends to do it locally.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
