[BUGS] deadlock_timeout and pg_ctl reload

2003-07-21 Thread A.Bhuvaneswaran
Hi, I am using pgsql 7.3.2. If we change the deadlock_timeout value in postgresql.conf and say pg_ctl reload, the new value is not taken affect. But any other changes like, datestyle, log_connection, log_pid, etc are taken affect immediately when we say pg_ctl reload. When we restart the server,

Re: [BUGS] deadlock_timeout and pg_ctl reload

2003-07-21 Thread Stephan Szabo
On Mon, 21 Jul 2003, A.Bhuvaneswaran wrote: > I am using pgsql 7.3.2. > > If we change the deadlock_timeout value in postgresql.conf and say pg_ctl > reload, the new value is not taken affect. But any other changes like, > datestyle, log_connection, log_pid, etc are taken affect immediately when

[BUGS] Silent deadlock

2003-07-21 Thread Boris Folgmann
Hi! We run a web application based on a complex database using postgresql-7.2.3-5.80 on Red Hat 8.0. Generally using pgsql with JDBC is very nice, but from time to time we run into problems that are caused by something like a silent deadlock, which means that it isn't reported in the logfile and

Re: [BUGS] deadlock_timeout and pg_ctl reload

2003-07-21 Thread Bruce Momjian
Stephan Szabo wrote: > > On Mon, 21 Jul 2003, A.Bhuvaneswaran wrote: > > > I am using pgsql 7.3.2. > > > > If we change the deadlock_timeout value in postgresql.conf and say pg_ctl > > reload, the new value is not taken affect. But any other changes like, > > datestyle, log_connection, log_pid, e

Re: [BUGS] deadlock_timeout and pg_ctl reload

2003-07-21 Thread Tom Lane
Bruce Momjian <[EMAIL PROTECTED]> writes: > Stephan Szabo wrote: >> It looks like deadlock_timeout is set PGC_POSTMASTER so it's not >> supposed to be reread on SIGHUP (reload) but only on postmaster start. > I think it doesn't reload because we want to have the same timeouts for > all backends, a

[BUGS] PostgreSQL 7.3.3 with pgcrypto on FreeBSD 5.1

2003-07-21 Thread Alex Rodin
POSTGRESQL BUG REPORT TEMPLATE Your name : Alexey Rodin Your email address : [EMAIL PRO

[BUGS] about PqSql

2003-07-21 Thread "Zaprian Gadev"
>From where I can download PgSql version for Windows(win32). 10x regards ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] Silent deadlock

2003-07-21 Thread Boris Folgmann
Hi! We run a web application based on a complex database using postgresql-7.2.3-5.80 on Red Hat 8.0. Generally using pgsql with JDBC is very nice, but from time to time we run into problems that are caused by something like a silent deadlock, which means that it isn't reported in the logfile and

Re: [GENERAL] [BUGS] INSTEAD rule bug?

2003-07-21 Thread DeJuan Jackson
Can we define the actual problem? Does it have to do with NEW and OLD with UNIONS?   Or is it simply any conditional rule using UNION/EXCEPT/INTERSECT/...? I ask because I'm confused by Tom's examples of failures. Tom Lane wrote: Dmitry Tkach <[EMAIL PROTECTED]> writes: Tom Lane

Re: [GENERAL] [BUGS] INSTEAD rule bug?

2003-07-21 Thread Tom Lane
DeJuan Jackson <[EMAIL PROTECTED]> writes: > Or is it simply any conditional rule using UNION/EXCEPT/INTERSECT/...? Yeah, that's about the size of it :-(. Note though that you could probably work around the problem by pushing the UNION etc. down into a sub-select: SELECT * FROM (SELECT