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

• Re: logging as inserts at 2005-03-03 21:17:00 from Tom Lane

Responses

• Re: logging as inserts at 2005-03-03 22:45:29 from Andrew Dunstan
• Re: logging as inserts at 2005-03-03 23:43:14 from Josh Berkus

pgsql-hackers by date

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