[BUGS] BUG #5468: Pg doesn't send accepted root CA list to client during SSL client cert request

2010-05-21 Thread Craig Ringer
The following bug has been logged online: Bug reference: 5468 Logged by: Craig Ringer Email address: cr...@postnewspapers.com.au PostgreSQL version: 8.4 Operating system: Ubuntu 10.04, but affects all Description:Pg doesn't send accepted root CA list to client during

Re: [BUGS] BUG #5468: Pg doesn't send accepted root CA list to client during SSL client cert request

2010-05-21 Thread Magnus Hagander
On Fri, May 21, 2010 at 7:52 AM, Craig Ringer wrote: > > The following bug has been logged online: > > Bug reference:      5468 > Logged by:          Craig Ringer > Email address:      cr...@postnewspapers.com.au > PostgreSQL version: 8.4 > Operating system:   Ubuntu 10.04, but affects all > Descr

[BUGS] psql or pgbouncer bug?

2010-05-21 Thread Jakub Ouhrabka
Hi, can anyone tell me how this could happen, please? database=# begin; update table set col = 100; server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. The connection to the server was lost. Attempti

Re: [BUGS] psql or pgbouncer bug?

2010-05-21 Thread Tom Lane
Jakub Ouhrabka writes: > can anyone tell me how this could happen, please? > database=# begin; update table set col = 100; > server closed the connection unexpectedly > This probably means the server terminated abnormally > before or while processing the request. > The connection

Re: [BUGS] psql or pgbouncer bug?

2010-05-21 Thread Stefan Kaltenbrunner
On 05/21/2010 11:19 AM, Jakub Ouhrabka wrote: > Hi, > > can anyone tell me how this could happen, please? > > database=# begin; update table set col = 100; > server closed the connection unexpectedly >This probably means the server terminated abnormally >before or while processing

Re: [BUGS] psql or pgbouncer bug?

2010-05-21 Thread Jakub Ouhrabka
> What's in the postmaster log? Excerpts from both postmater and pgbouncer logs see below. I can't find nothing more interesting, no errors. There is difference between server clocks, pgbouncer is 40s behind postgresql server, will fix... Kuba Postmaster: 2010-05-21 15:58:58 CEST 20436 1

Re: [BUGS] psql or pgbouncer bug?

2010-05-21 Thread Jakub Ouhrabka
Hi Stefan, thanks - but I don't understand how could the BEGIN; UPDATE xxx; be committed to database without explicit COMMIT and how could psql report "UPDATE 153" after message "The connection was reset". This puzzles me... Kuba Dne 21.5.2010 17:33, Stefan Kaltenbrunner napsal(a): On 05/21

Re: [BUGS] psql or pgbouncer bug?

2010-05-21 Thread Stefan Kaltenbrunner
On 05/21/2010 12:03 PM, Jakub Ouhrabka wrote: > Hi Stefan, > > thanks - but I don't understand how could the BEGIN; UPDATE xxx; be > committed to database without explicit COMMIT and how could psql report > "UPDATE 153" after message "The connection was reset". This puzzles me... hmm yeah that is

Re: [BUGS] psql or pgbouncer bug?

2010-05-21 Thread Jakub Ouhrabka
> hmm yeah that is indeed a tad weird - are you actually using as > pool_mode and server_reset_query? pool_mode = session server_reset_query = RESET ALL; SET SESSION AUTHORIZATION DEFAULT; UNLISTEN *; Kuba -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to you

Re: [BUGS] psql or pgbouncer bug?

2010-05-21 Thread Stefan Kaltenbrunner
On 05/21/2010 12:13 PM, Jakub Ouhrabka wrote: >> hmm yeah that is indeed a tad weird - are you actually using as >> pool_mode and server_reset_query? > > pool_mode = session > > server_reset_query = RESET ALL; SET SESSION AUTHORIZATION DEFAULT; > UNLISTEN *; hmm - and you are really sure that th

Re: [BUGS] psql or pgbouncer bug?

2010-05-21 Thread Tom Lane
Jakub Ouhrabka writes: >>> What's in the postmaster log? > Excerpts from both postmater and pgbouncer logs see below. I can't find > nothing more interesting, no errors. Looks like the disconnect was because pgbouncer restarted. If that wasn't supposed to happen then you should take it up with

Re: [BUGS] psql or pgbouncer bug?

2010-05-21 Thread Tom Lane
Jakub Ouhrabka writes: > Tom: >>> Looks like the disconnect was because pgbouncer restarted. If that >>> wasn't supposed to happen then you should take it up with the >>> pgbouncer folk. > The restart of pgbouncer was intentional, although made by someone else, > so the disconnect is ok. What's

Re: [BUGS] psql or pgbouncer bug?

2010-05-21 Thread Stefan Kaltenbrunner
On 05/21/2010 01:32 PM, Tom Lane wrote: > Jakub Ouhrabka writes: >> Tom: Looks like the disconnect was because pgbouncer restarted. If that wasn't supposed to happen then you should take it up with the pgbouncer folk. > >> The restart of pgbouncer was intentional, although made by

Re: [BUGS] psql or pgbouncer bug?

2010-05-21 Thread Jakub Ouhrabka
Tom: > Looks like the disconnect was because pgbouncer restarted. If that > wasn't supposed to happen then you should take it up with the > pgbouncer folk. The restart of pgbouncer was intentional, although made by someone else, so the disconnect is ok. What's not ok is the "UPDATE 153" messag

Re: [BUGS] BUG #5468: Pg doesn't send accepted root CA list to client during SSL client cert request

2010-05-21 Thread Craig Ringer
On 21/05/2010 10:35 PM, Magnus Hagander wrote: On Fri, May 21, 2010 at 7:52 AM, Craig Ringer wrote: The following bug has been logged online: Bug reference: 5468 Logged by: Craig Ringer Email address: cr...@postnewspapers.com.au PostgreSQL version: 8.4 Operating system: