I wrote:
> I will try to measure overheads of logging in some implementation:
> 1. Log statements and dump them into server logs.
> 2. Log statements and filter them before to be written.
> 3. Store statements in shared memory.
> I know 1 is slow, but I don't know what part of it is really sl
Josh,
Can i hope to your interest ?
>>> I stated details of proposal on page 2-13, 67-75 of pdf-document
>>> http://sql50.euro.ru/sql5.16.4.pdf , and i ask to implement it.
>>> All my proposals are public domain.
JB>> I'm confused. You're planning to develop this
DT> I can't make this alone.
JB>
FYI, I will be presenting at this Tuesday evening's New York PHP
meeting. I will be mostly talking about EnterpriseDB's Postgres Plus:
http://www.nyphp.org/index.php
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://enterpr
On Friday 20 June 2008 12:19:03 Joshua D. Drake wrote:
> On Fri, 2008-06-20 at 13:10 +0530, Deepak wrote:
> > Hi
> >
> > I am trying to create a TRIGGER function,that populates values to
> > another table upon inserting a value into a table. The issue is,if
> > there is a exception(in Table 2) ever
Thomas Lee wrote:
> Thanks for the feedback Tom. An initial patch for this has been posted
> to pgsql-patches.
Thanks for the patch. I have added it to the current Commitfest wiki
page. If you plan to continue sending patches, please make sure you get
an account to do that yourself. Thanks.
Thanks for the feedback Tom. An initial patch for this has been posted
to pgsql-patches.
Cheers,
T
Tom Lane wrote:
Thomas Lee <[EMAIL PROTECTED]> writes:
How does this sound:
* A new GUC variable -- "activity_message_size" -- will be introduced
Well, "message" doesn't see
