| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Bradley Holbrook <operations_bradley(at)servillian(dot)ca> |
| Cc: | "French, Martin" <frenchm(at)cromwell(dot)co(dot)uk>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Postgres Backup Utility |
| Date: | 2011-01-20 18:49:26 |
| Message-ID: | AANLkTikOdsjzGFMpti_P9+yuFGP08jA_QL1_vbBJd=uB@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, Jan 20, 2011 at 10:52 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> Followup, note that you can set the log_statement='ddl' for an entire
> pg cluster, for a single database, or for a single user, if that
> helps. logging ddl does not log dml, or data changes, just structural
> changes.
also also wik, you can use the log_line_prefix to make it so that you
can grep out what you need easier too.
#log_line_prefix = '' # special values:
# %u = user name
# %d = database name
# %r = remote host and port
# %h = remote host
# %p = process ID
# %t = timestamp without milliseconds
# %m = timestamp with milliseconds
# %i = command tag
# %c = session ID
# %l = session line number
# %s = session start timestamp
# %v = virtual transaction ID
# %x = transaction ID (0 if none)
# %q = stop here in non-session
# processes
# %% = '%'
# e.g. '<%u%%%d> '
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Neyman | 2011-01-20 21:17:58 | Re: Postgres Backup Utility |
| Previous Message | Chris Browne | 2011-01-20 18:01:36 | Re: State of multi-master replication options |