Many thanks for your helpful suggestions
To answer your question about 'log_statement' not appearing to handle SELECT
statements: could be a documentation omission. I got that from version 8.0.1
documentation PDF, p 268, section 16.4.6.3 where 'log_statement(string)' is
discussed:
http://www
On Fri, 2005-11-11 at 17:04 -0600, Judith Altamirano Figueroa wrote:
> Hi
>
> how could I restore a db if I did next:
>
> pg_dump -Z 9 soi > $DESTINO/soi.bkp
Since you don't specify any dump format, your dump should be plain text
and is compressed with gzip, so the restore command is going t
> We are putting a new application on PostgreSQL 8.0.1 (Windows
> 2003); we are coming off of MySQL, and are having a hard time
> finding all of the offending SQL calls.
>
> It would help a great deal if I could log the content of any
> SQL calls that fail. Am only interested in SELECT statemen
Lane Van Ingen wrote:
We are putting a new application on PostgreSQL 8.0.1 (Windows 2003);
we are coming off of MySQL, and are having a hard time finding all of
the offending SQL calls.
It would help a great deal if I could log the content of any SQL calls
that fail. Am only interested in SELECT
