On Wed, Nov 23, 2011 at 9:28 PM, Theo Schlossnagle <jesus(at)omniti(dot)com> wrote:
> We have a need for logging in systems where it isn't feasible to log
> to disk as it negatively impacts performance.
> I'd like to be able to creatively solve this problem without modifying
> the core, but today I cannot.
> So... here's my first whack at solving this with some flexibility.
> The first thing I did was add hook points where immediate statement
> logging happens "pre_exec" and those that present duration
> "post_exec". These should, with optimization turned on, have only a
> few instructions of impact when no hooks are registered (we could
> hoist the branch outside the function call if that were identified as
> an issue).
> The second thing I did was write a sample use of those hooks to
> implement a completely non-blocking fifo logger. (if it would block,
> it drops the log line). The concept is that we could run this without
> risk of negative performance impact due to slow log reading (choosing
> to drop logs in lieu of pausing). And a simple process could be
> written to consume from the fifo. We use this method in other systems
> to log many 10s of thousands of log lines per second with negligible
> impact on performance.
> Thoughts? Feedback?
> As can be seen, the patch is pretty tiny.
Tom recently committed something by another author that is along
similar lines to what you have here (I think). Can you comment on
whether you think more is still needed and what the differences are
between that approach and yours?
The Enterprise PostgreSQL Company
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2012-03-09 14:55:09|
|Subject: Re: xlog location arithmetic |
|Previous:||From: Tom Lane||Date: 2012-03-09 14:48:51|
|Subject: Re: pgsql_fdw, FDW for PostgreSQL server |