2010/1/12 Omar Mehmood :
> Is there any way to enable transaction logging in the format of SQL
> statements for committed transactions only ? In other words, a way to log
> all the SQL statements (including START TRANSACTION and COMMIT statements)
> for all committed mod type statements (INSERT
Use
log_min_duration_statement=0
at postgresql.conf file to log every statement.
On Tue, Jan 12, 2010 at 7:50 AM, Omar Mehmood wrote:
> Is there any way to enable transaction logging in the format of SQL
> statements for committed transactions only ? In other words, a way to log
> all the SQL
Is there any way to enable transaction logging in the format of SQL statements
for committed transactions only ? In other words, a way to log all the SQL
statements (including START TRANSACTION and COMMIT statements) for all
committed mod type statements (INSERT UPDATE DELETE etc).
Thanks,
Oma
On Fri, May 16, 2008 at 1:06 PM, Michael P. Soulier
<[EMAIL PROTECTED]> wrote:
> I'm interested in enabling transaction logging, so that I can audit those
> logs on a system having issues.
>
> Is there already such a log in postgres 7.4? If not, is there such a feature
> and how do I enable it?
>
>
I'm interested in enabling transaction logging, so that I can audit
those logs on a system having issues.
Is there already such a log in postgres 7.4? If not, is there such a
feature and how do I enable it?
I looked in the docs and saw many logging options but nothing for
transactions.
Tha
Updated TODO:
* Transaction log, so re-do log can be on a separate disk by
with after-row images
> > Added to TODO:
> >
> > * Transaction log, so re-do log can be on a separate disk by
> > logging SQL queries, or before/after row images
> >
> I would drop the "log SQL queries ide
> Added to TODO:
>
> * Transaction log, so re-do log can be on a separate disk by
> logging SQL queries, or before/after row images
>
I would drop the "log SQL queries idea".
No need to log before row images eighter, since this is the
current state of the row during rollforward.
> What would it take to have transaction logging added to Postgres. I am a
> c/c++ programmer and will consider contributing to the Postgres development
> effort. I really like everything I see and read about Postgres. As a
> result, I am strongly considering Postgres as the database engine for