Re: [BUGS] Logging problems in PostgreSQL 7.2devel

2001-09-10 Thread John Summerfield
On Fri, 7 Sep 2001, Tom Lane wrote: > John Summerfield <[EMAIL PROTECTED]> writes: > > I have postmaster configured to use syslog. Despite this, these messages appear on >the terminal from which I start it: > > 2001-09-03 23:44:37 [26371] DEBUG: recycled transaction log file 0044

Re: [BUGS] parse error: LIMIT combined with UNION

2001-09-10 Thread Steve Pothier
Tom, You are correct. My humblest apologies. When I did the test it was on a machine not local to the database. The client machine was running psql 7.1 but the server is (apparently) 7.0.3. I say "apparently" because I'm not sure how to find the version of the server! I just assume that the

Re: [BUGS] Conditional NOTIFY is not implemented

2001-09-10 Thread matthew.copeland
On Fri, 7 Sep 2001 [EMAIL PROTECTED] wrote: > On Fri, Sep 07, 2001 at 12:30:44AM -0400, Tom Lane wrote: > > [EMAIL PROTECTED] writes: > > > My pattern of use for ``CREATE RULE... NOTIFY...'' was [...] > > > Yeah, that is the normal and recommended usage pattern for NOTIFY, so > > getting a NOTI

[BUGS] BUG in 7.1.3 (fwd)

2001-09-10 Thread Alessandro Rossi
I think I have found a bug in version 7.1.3. (I have installed binary rpms from postgres site on rh7.1) Here is the DB and some sample entries. CREATE TABLE "timetest" ( "id" serial primary key, "timebegin" time, "timeend" time ); insert into timetest (timebe

[BUGS] ecpg incompatibility with DB2

2001-09-10 Thread John Summerfield
This is explicity allowed in db2: void f3(int i) { EXEC SQL BEGIN DECLARE SECTION; char host_var_3[25]; EXEC SQL END DECLARE SECTION; EXEC SQL SELECT COL2 INTO :host_var_3 FROM TBL2; } void f4(int i) { char host_var_3[25]; EXEC SQL INSERT I

[BUGS] Trouble in SELECT query

2001-09-10 Thread Serg Matskov
I have a PostgreSQL 7.1. When I start query like "SELECT * FROM table1 WHERE field1 = NULL;" it working OK, but query like "SELECT * FROM table1 WHERE field1 <> NULL" returns the void result. Field "field1" has type DATE. "... field1 IS NULL", "... field1 IS NOT NULL", "... field1 <> 0" also

[BUGS]

2001-09-10 Thread Valery Kocubinsky
      POSTGRESQL BUG REPORT TEMPLATE   Your name  : Valery KocubinskyYour email address :[EMAIL PROTECTED]   System Confi

Re: [BUGS] Trouble in SELECT query

2001-09-10 Thread Peter Eisentraut
Serg Matskov writes: > I have a PostgreSQL 7.1. When I start query like "SELECT * FROM table1 > WHERE field1 = NULL;" it working OK, but query like "SELECT * FROM > table1 WHERE field1 <> NULL" returns the void result. Field "field1" > has type DATE. "... field1 IS NULL", "... field1 IS NOT NULL"

Re: [BUGS] Build problem with CVS version

2001-09-10 Thread John Summerfield
> Tom Lane writes: > > > > What we probably want is some configure switch that switches between the > > > current behaviour and the behaviour you want. > > > > I'd suggest --prefix-like options to determine installation locations > > for the perl and python modules, > > Basically, I was envision

Re: [HACKERS] [BUGS] Build problem with CVS version

2001-09-10 Thread Lamar Owen
On Thursday 06 September 2001 07:46 pm, John Summerfield wrote: > I'd point out this from the INSTALL document: > --prefix=PREFIX [snip] > Installing everything under --prefix (as the document says) would also > help package builders; the current rpm looks pretty horrible (and > that's why I