Re: PostgreSQL roadmap for 8.2 and beyond.

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: patrick(at)vanbelle(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PostgreSQL roadmap for 8.2 and beyond.
Date: 2005-10-18 09:29:58
Message-ID: 4354C096.4060703@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

>Patrick Bakker <patrick(at)vanbelle(dot)com> writes:
>
>
>>It would be useful if you could toggle SQL statement logging without
>>restarting PostgreSQL and additionally if you could turn on selective SQL
>>logging. Additionally, it would be great if you could log SQL statements to
>>a separate file from the main log and in such a way that the statements are
>>seperated in an easily parsed form.
>>
>>
>
>
>
>>The runtime toggling of statement logging would also be most useful if you
>>could toggle it outside of a particular session. This is where the selective
>>SQL logging would be useful I think. Some selectable options that could be
>>useful:
>> - by database
>> - by user
>> - by IP address
>>
>>
>
>You do realize that the majority of that can be done today? You need to
>study the available mechanism for setting GUC parameters a little more.
>
>
Not quite, if you want to set it on databases you're not connected to,
i.e. if you want to 'tap' a backend.

Regards,
Andreas

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2005-10-18 09:35:27 Re: Problem in ExecEvalExpr function
Previous Message sandeep satpal 2005-10-18 09:08:39 Problem in ExecEvalExpr function