Gavin Hamill wrote:
On Sun, 09 Apr 2006 17:00:14 +0100
Simon Riggs <[EMAIL PROTECTED]> wrote:
Sniff the live log for SELECT statements (plus their live durations),
Wow, how wonderfully low-tech - hence it's right up my street :) Yay,
some tail + psql fun coming up!
Be careful though - concu
On Sun, 09 Apr 2006 17:00:14 +0100
Simon Riggs <[EMAIL PROTECTED]> wrote:
> On Sat, 2006-04-08 at 15:10 +0100, Gavin Hamill wrote:
>
> > SELECTS go to *both* live and test, but only the answers from live
> > are sent back to clients - the answers from test are discarded...
>
> Put log_min_durat
Gavin Hamill wrote:
On Sun, 09 Apr 2006 17:00:14 +0100
Simon Riggs <[EMAIL PROTECTED]> wrote:
Sniff the live log for SELECT statements (plus their live durations),
Wow, how wonderfully low-tech - hence it's right up my street :) Yay,
some tail + psql fun coming up!
You can even tell it to o
On Sun, 09 Apr 2006 17:00:14 +0100
Simon Riggs <[EMAIL PROTECTED]> wrote:
> Sniff the live log for SELECT statements (plus their live durations),
Wow, how wonderfully low-tech - hence it's right up my street :) Yay,
some tail + psql fun coming up!
Cheers,
Gavin.
---(end
On Sat, 2006-04-08 at 15:10 +0100, Gavin Hamill wrote:
> SELECTS go to *both* live and test, but only the answers from live are
> sent back to clients - the answers from test are discarded...
Put log_min_duration_statement = 0 so all SELECTs go to the log.
Sniff the live log for SELECT statemen
Hi,
I'm asking here in case this kind of thing has been done before, but
I've not been able to find it..
We have two pg 8.1.3 servers, one live and one test. What I'd like to do
is have something like pgpool to act as a connection broker, but
instead of using pgpool's own replication where all qu
