Re: logging as inserts

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, jd(at)commandprompt(dot)com
Subject: Re: logging as inserts
Date: 2005-03-03 22:14:50
Message-ID: 200503031414.50818.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom,

> But log_line_prefix works fine for all destinations, which is exactly
> why this new facility isn't a destination. You're just confusing
> matters by wanting to treat it as one.

Hmmm ... hey, if we just allowed extra text in log_line_prefix, and allowed %$
to enclose the statement with literal quoting, you could do this all through
log_line_prefix, as:

log_line_prefix='INSERT INTO pg_log VALUES ( %u, %p, ''%t'', ''%$'')'

--
--Josh

Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2005-03-03 22:45:29 Re: logging as inserts
Previous Message Tom Lane 2005-03-03 22:05:40 Solving hash table overrun problems