[BUGS] Bug #823: upper() does not handle å, ä and ö correctly.

[pgsql-bugs]

Marcus Andersson ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
upper() does not handle å, ä and ö correctly.

Long Description
The function upper() just leaves the letters å, ä, and ö unmodified. It should replace 
them with Å, Ä and Ö respectively.

PostgreSQL version 7.2.3 on Solaris.

I am using encoding 7 (ISO 8859-1).

Sample Code


No file was uploaded with this report


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] RULE: ON DELETE doesn't stack deletes

[Malcolm Hutty]

According to the manual you can stack multiple queries in a RULE:

CREATE RULE name AS ON event
TO object [ WHERE condition ]
DO [ INSTEAD ] action

where action can be:

NOTHING
|
query
|
( query ; query ... )
|
[ query ; query ... ]


This seems to work provided 'query' is not "DELETE"; if it is, only 
the first one is executed.

My installation is Postgres 7.2.2, using the binary package shipped in 
Redhat 8.0

[malcolm@localhost STRUCT]$ uname -sr
Linux 2.4.18-18.8.0


Here is a test case:

CREATE TABLE A
(a_data int);

CREATE TABLE B
(b_data int);

CREATE VIEW V_AB AS
SELECT a_data,b_data FROM A,B;

CREATE RULE R_DEL_AB AS
ON DELETE TO V_AB
DO INSTEAD
(
DELETE FROM A WHERE a_data=OLD.a_data;
DELETE FROM B WHERE b_data=OLD.b_data;
);

INSERT INTO A values (1);
INSERT INTO B values (1);


test=# select * from V_AB;
 a_data | b_data
+
  1 |  1
(1 row)


test=#delete from v_ab;
DELETE 0

test=# select * from a;
 a_data

(0 rows)

test=# select * from b;
 b_data

  1
(1 row)



---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

[BUGS] version for sun cobalt qube 3

[Weber Gerhard]

Title: version for sun cobalt qube 3





dear reader


we have a cobalt qube 3 with an old version 6.5 of postgresql. we use postgresql 7.2.3 on other platforms like windows.


what we have to do for installing the mentioned, newest version on our cobalt qube 3? wich version we hav to download? how to install  on it?

thank you very much in advance.


best regards


Gerhard Weber 


  --  
Telefon: +41 (0)55 415 30 30  --  FAX: +41 (0)55 415 30 31
Post: Churerstrasse 22, Postfach, CH-8808 Pfäffikon SZ 


Nicht lesen!
Java(tm)/J2EE-EJB(tm) Web-PORTAL 
mit Web-Content und -Applikationen zum Probieren.
-> Einfach, sicher, schnell und günstig (ökonomisch). 

[BUGS] dbmirror bug

[Hai-Chen Tu]

Your name   : Hai-Chen Tu
Your email address  : [EMAIL PROTECTED]


System Configuration
-
  Architecture (example: Intel Pentium) :

  Operating System (example: Linux 2.0.26 ELF)  :

  PostgreSQL version (example: PostgreSQL-7.3):  
PostgreSQL-7.3

  Compiler used (example:  gcc 2.95.2)  :


Please enter a FULL description of your problem:

dbmirror generates "out of memory" error in some
cases when the DEBUG_OUTPUT is enabled.




Please describe a way to repeat the problem.   Please
try to provide a
concise reproducible example, if at all possible: 
--
The cause of the problem is that dbmirror
uses
elog(NOTICE, cpKeyData)
and
elog(NOTICE, cpFieldData)
to print column data where elog
interprets the second argument as sprintf
format string, which fails if
cpKeyData/cpFieldData contains '%'.




If you know how this problem might be fixed, list the
solution below:
-

The solution is to change
elog(NOTICE, ...)
to
elog(NOTICE, "%s", ...)

This applies to all cpKeyData and cpFieldData,
and probably cpFieldName(?).


__
Do you Yahoo!?
Yahoo! Web Hosting - Let the expert host your site
http://webhosting.yahoo.com

---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

[BUGS] Can't start postmaster on Cygwin with local 'ja_JP.EUC

[Tamotsu Ebina]

Dear Sirs,
(B
(BI maked postgresql using postgresql-7.3rc1 on WindowsXPProfessional+CygWin,
(B
(B$ ./configure --enable-multibyte=EUC_JP --enable-locale --with-CXX --with-java
(B--enable-odbc
(B
(Bwith no error.
(B
(Binitdb finished also with no error.
(B
(BBut I can't start postmaster.
(B
(B$ postmaster  -i&
(B[2] 472
(B
(Bebina@HAYAMA02 /usr/local/pgsql/postgresql-7.3rc1
(B$ FATAL:  invalid value for option 'LC_MESSAGES': 'ja_JP.EUC'
(B
(B[2]+  Exit 1  postmaster -i
(B
(BWhat shoul'd I do? 
(B(postgresql-7.2.3 works well on Cygwin with same condition.)
(B
(BThank you in advance.
(B
(BTamo
(B
(B--
(Boffice  [EMAIL PROTECTED]  http://www.iftc.co.jp/
(BTel +81-3-3360-6514 Fax +81-3-3360-7411
(Bprivate [EMAIL PROTECTED]  http://www.pluto.dti.ne.jp/~ebina/
(B[Amateur Radio Station JCG#11007 JA1QKK ] Tamotsu Ebina
(B
(B
(B
(B---(end of broadcast)---
(BTIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] Minor build nits in 7.3rc1

[Harris Peter]

Hi

1)
configure fails too easily if your libraries and include files are in a
funny place. When you specify --prefix=/somewhere, maybe it should use "-L
/somewhere/lib" and "-I/somewhere/include" by default when checking if
things exist.
Workaround: I had to add the options to LDFLAGS and CPPFLAGS myself to get
readline noticed.

2)
The makefile contains many rm.  I usually like to alias rm="rm -i" for
safety, so I had to answer (y/n) a lot of times.  Could the makefile please
use rm -f?

Thanks


Peter Harris
Kyndal Spirits



This message and any files transmitted with it are confidential.  
The contents may not be disclosed or used by anyone other 
than the addressee. 
If you have received this communication in error, please delete 
the message and notify Kyndal International Limited immediately 
on 0141-248-5771.

The views expressed in this email are not necessarily the views 
of Kyndal International Limited.  
As it has been transmitted over a public network, 
Kyndal International Limited makes no representation nor accepts 
any liability for the email's accuracy or completeness unless 
expressly stated to the contrary.

Should you, as the intended recipient, suspect that the message 
has been intercepted or amended, please notify 
Kyndal International Limited immediately on 0141-248-5771.



---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

[BUGS] MemoryContextAllc error.

[ricky]

i was trying to back up db from the 
server.
i found the error while i was trying to 
backup.
 
bash$ /usr/local/pgsql/bin/pg_dumpall > 
db.out
ERROR:  
MemoryContextAlloc: invalid request size 4294967293
PQendcopy: resetting connection
SQL 
query to dump the contents of Table 't_oommain' did not execute correctly.  After we read all the table contents 
from the backend, PQendcopy() failed.  
Explanation from backend: 'ERROR:  
MemoryContextAlloc: invalid request size 4294967293
'.
The 
query was: 'COPY "t_oommain" TO stdout;
'.
pg_dump 
failed on xenodb, exiting
 
what 
shall i do here?
please 
give me the solution for this problem.
Thank 
you very much.

Re: [BUGS] posgres on win2k, install cygipc

[Merlin Moncure]

in the win2k environment, I would consider adding the path to the
Cygwin1.dll to the system path (for example, c:\cygwin\bin)

then, using command prompt shell, not the CYGWIN shell, cd to the folder
containing the ipc-daemon.

>From there, type ipc-daemon to run the daemon
or ipc-daemon --install-as-service to install it as a service

""* *"" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> I'm trying to install postgres on my win2k pro computer.  Also I'm not
> familiar with the Linux OS.  I downloaded all the necessary software.  I
> installed cygwin but I'm having problems with cygipc.  I've extracted
cygipc
> to
>
> \usr\local\cygipc
>
> In the shell I type in ipc-daemon.exe and I get the message that it cannot
> be found.  Can someone help me out on this?
>
>
>
> _
> Send and receive Hotmail on your mobile device: http://mobile.msn.com
>
>
> ---(end of broadcast)---
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to [EMAIL PROTECTED] so that your
> message can get through to the mailing list cleanly



---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] Regarding Bug

[Prasad, Pati]

Hello
I am pati presently working iin research
oraganisation(Fraunhofer),Germany.Recently i ahve deployed a web application
connecting to the database postgre sql.
When i am connecting to the database i am getting the error of
postgresql.stream.flush and postgresql.stream.io some times.
please let me know how to solve it.
Thanking you
pati

---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

[BUGS] Help me~! MemoryContextAlloc Error 1!! Major bug

[i]

bash$ /usr/local/pgsql/bin/pg_dumpall > db.out
ERROR:  MemoryContextAlloc: 
invalid request size 4294967293
PQendcopy: resetting connection
SQL query to dump the contents of Table 't_oommain' did not execute 
correctly.  After we read all the 
table contents from the backend, PQendcopy() failed.  Explanation from backend: 'ERROR:  MemoryContextAlloc: invalid request size 
4294967293
'.
The query was: 'COPY "t_oommain" TO stdout;
'.
pg_dump failed on fms2000e, exiting
bash$
 
what shall i do???
i'm using postgresql 7.1.2 on RH 6.2
please give me some advise
thank you.

[BUGS] About timestamp and timestamptz

[Frédéric SURLEAU]

   
  Hi,
   
  I think there is a problem with the timestamp types in postgresql 
  7.2.3.
   
  In the documentation here http://www.postgresql.org/idocs/index.php?datatype.html the 
  table  3-1 says:
   
   
  
  


  timestamp [ (p) ] without time zone
  timestamp
  date and time

  timestamp [ (p) ] [ with time zone ]
  timestamptz
  date and time, including time 
zone
   
   
  So if I use the type "timestamp", it will not use the alias 
  "timestamp" for "timestamp without time 
  zone", but it will use a "timestamptz" because "with time zone" is 
  optional.
   
  Conclusion :
   
  1- To have a timestamp without time 
  zone I must say "timestamp without time zone"
  2- The alias "timestamp" can't be used and 
  should be removed or replaced.
   
  Or the table should be :
   
  
  


  timestamp [ (p) ] [ without time zone ]
  
  date and time

  timestamp [ (p) ] with time zone
  timestamptz
  date and time, including time 
zone
  like it's the case for time : 
  
  


  time [ (p) ] [ without time zone ]
   
  time of day

  time [ (p) ] with time zone
  timetz
  time of day, including time 
zone
  Regards,
  Fred.
  PS in real world, I can use "timestamp with time zone", but I 
  have the problem when using PhpPgAdmin, who reads the datatypes 
  available from "pg_type" where only aliases are listed.
  I tried to fix the problem in PhpPgAdmin looking for another way to 
  read data-types, but I didn't found it.







  IncrediMail - La messagerie électronique a enfin 
évolué - Cliquer 
ici

[BUGS] Pgsqlv7.3RC1, pgadminII v 1.4.0 Dropping a field does not drop asociate foreign key

[Rafael Villalobos Prats]

I have the next table:

CREATE TABLE aenor_subexpediente (
  id_aenor_subexpediente int4 DEFAULT
nextval('"aenor_subexpe_id_aenor_sube_seq"'::text) NOT NULL, 
  subexpediente varchar(30), 
  id_tecnico int4, 
  id_delegacion int4, 
  id_contacto int4, 
  id_cnae int4, 
  alcance_certificacion varchar(100), 
  id_t_aenor_subexpediente int4, 
  id_area int4, 
  CONSTRAINT aenor_subexpediente_pkey PRIMARY KEY
(id_aenor_subexpediente), 
  CONSTRAINT id_area_fk FOREIGN KEY (id_area) REFERENCES tm_area
(id_area) ON DELETE SET NULL ON UPDATE CASCADE NOT DEFERRABLE INITIALLY
IMMEDIATE, 
  CONSTRAINT id_cnae_fk FOREIGN KEY (id_cnae) REFERENCES cnae (id_cnae)
ON DELETE SET NULL ON UPDATE CASCADE NOT DEFERRABLE INITIALLY IMMEDIATE,

  CONSTRAINT id_contacto_fk FOREIGN KEY (id_contacto) REFERENCES
contactos (id_contacto) ON DELETE SET NULL ON UPDATE CASCADE NOT
DEFERRABLE INITIALLY IMMEDIATE, 
  CONSTRAINT id_delegacion_fk FOREIGN KEY (id_delegacion) REFERENCES
tm_delegaciones (id_delegacion) ON DELETE SET NULL ON UPDATE CASCADE NOT
DEFERRABLE INITIALLY IMMEDIATE, 
  CONSTRAINT id_t_aenor_subexpediente_fk FOREIGN KEY
(id_t_aenor_subexpediente) REFERENCES t_aenor_subexpediente
(id_t_aenor_subexpediente) ON DELETE SET NULL ON UPDATE CASCADE NOT
DEFERRABLE INITIALLY IMMEDIATE, 
  CONSTRAINT id_tecnico_fk FOREIGN KEY (id_tecnico) REFERENCES
tm_tecnicos (id_tecnico) ON DELETE SET NULL ON UPDATE CASCADE NOT
DEFERRABLE INITIALLY IMMEDIATE
) WITH OIDS;

I have dropped a field with pgadmin 1.4.0 but the FK is not DROPPED and 
If i try insert a record in this table i get hext error: constraint
id_tecnico_fk: table aenor_subexpediente does not have  an attribute
id_tecnico
when i try dropping the fk i get the error that it does not exist,  

Rafa


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

[BUGS] vacumm error

[Stefanos Harhalakis]

I'm running postgresql 7.2.1 on linux.

I cannot run vacuumm on a table in a database i'm running for about 7 months.
I get:

ERROR:  No one parent tuple was found

I've found an older posting about that but the poster said that after 
restarting it was fixed. In my case this is not true. I've restarted 
postgresql but it didn't work. Noone else is trying to use this database 
(other databases are used).

test=> vacuum full analyze verbose entities;
NOTICE:  --Relation entities--
NOTICE:  Pages 312833: Changed 107130, reaped 273241, Empty 0, New 0; Tup 
9895954: Vac 9005277, Keep/VTL 0/0, UnUsed 44715182, MinLen 36, MaxLen 36; 
Re-using: Free/Avail. Space 1945751280/1945279044; EndEmpty/Avail. Pages 
0/273480.
CPU 31.30s/9.81u sec elapsed 138.29 sec.
NOTICE:  Index entities_pkey: Pages 277210; Tuples 9895954: Deleted 9005277.
CPU 33.33s/75.02u sec elapsed 401.49 sec.
ERROR:  No one parent tuple was found

I had fsync=false in postgresql.conf and the machine crashed but i didn't
notice anything strange since then. I've seen the database to grow up each
day after i did a kill -9 to two db backends. At that time postgre restarted
telling me that the shared memory area is possibly corrupted.

The table entities is an one column table (don't ask why :):

test=# \d entities
 Table "entities"
 Column |  Type   |   Modifiers
+-+
 id | integer | not null default nextval('seq_entities'::text)
Primary key: entities_pkey
Triggers: RI_ConstraintTrigger_26872259,
  RI_ConstraintTrigger_26872261,
  RI_ConstraintTrigger_26872268,
  RI_ConstraintTrigger_26872270,
  RI_ConstraintTrigger_26872277,
  RI_ConstraintTrigger_26872279,
  RI_ConstraintTrigger_26872286,
  RI_ConstraintTrigger_26872288,
  RI_ConstraintTrigger_26872295,
  RI_ConstraintTrigger_26872297,
  RI_ConstraintTrigger_26872304,
  RI_ConstraintTrigger_26872306,
  RI_ConstraintTrigger_26872313,
  RI_ConstraintTrigger_26872315,
  RI_ConstraintTrigger_26872323,
  RI_ConstraintTrigger_26872325,
  RI_ConstraintTrigger_26872333,
  RI_ConstraintTrigger_26872335,
  RI_ConstraintTrigger_26872343,
  RI_ConstraintTrigger_26872345,
  RI_ConstraintTrigger_26872353,
  RI_ConstraintTrigger_26872355,
  RI_ConstraintTrigger_26872250,
  RI_ConstraintTrigger_26872252,
  RI_ConstraintTrigger_101919110,
  RI_ConstraintTrigger_101919112

I'm currently running vacumm full on another (larger) table 
(table entities has 312K pages and this one has 1.3M pages)

TIA

<>


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [BUGS] like not using indexes in 7.3b5?

[andrzej]

okk
U¿ytkownik "Tom Lane" <[EMAIL PROTECTED]> napisa³ w wiadomo¶ci
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Lars <[EMAIL PROTECTED]> writes:
> > Is that expected behavior in 7.3?
>
> It is if you initdb'd in a locale other than "C".  Use pg_controldata
> to check.
>
> regards, tom lane
>
> ---(end of broadcast)---
> TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]



---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

[BUGS] Compile problem postgresql-7.3rc1 and Mac OS X 10.2.2

[Rickard Annell]

system info:
Mac OS X v 10.2.2 (Darwin Kernel Version 6.2: Tue Nov  5 22:00:03 PST 
2002; root:xnu/xnu-344.12.2.obj~1/RELEASE_PPC)
Java build 1.3.1_03-69, mixed mode
Ant version 1.5
gcc  Apple Computer, Inc. GCC version 1161, based on gcc version 3.1 
20020420 (prerelease)
postgres 7.3rc1



./configure --prefix=/service/database/postgres --with-java

make


last rows from make command


make[5]: Nothing to be done for `all'.
/service/www/jakarta/ant/bin/ant -buildfile ./build.xml all \
  -Dmajor=7 -Dminor=3 -Dfullversion=7.3rc1 -Ddef_pgport=5432 -Denable_debug=no
Buildfile: ./build.xml

all:

prepare:

check_versions:

driver:
 [copy] Copying 1 file to 
/usr/local/src/postgresql-7.3rc1/src/interfaces/jdbc/org/postgresql
 [echo] Configured build for the JDBC2 edition driver

compile:
[javac] Compiling 25 source files to 
/usr/local/src/postgresql-7.3rc1/src/interfaces/jdbc/build
[javac] 
/usr/local/src/postgresql-7.3rc1/src/interfaces/jdbc/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java:240: 
cannot resolve symbol
[javac] symbol  : constructor Array 
(org.postgresql.PGConnection,int,org.postgresql.Field,java.sql.ResultSet)
[javac] location: class org.postgresql.jdbc2.Array
[javac] return (java.sql.Array) new 
org.postgresql.jdbc2.Array( connection, i, fields[i - 1], 
(java.sql.ResultSet) this );
[javac] ^
[javac] 
/usr/local/src/postgresql-7.3rc1/src/interfaces/jdbc/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java:420: 
incompatible types
[javac] found   : java.sql.Statement
[javac] required: org.postgresql.jdbc2.Statement
[javac] return statement;
[javac]^
[javac] 
/usr/local/src/postgresql-7.3rc1/src/interfaces/jdbc/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java:560: 
incompatible types
[javac] found   : java.sql.PreparedStatement
[javac] required: org.postgresql.jdbc2.PreparedStatement
[javac] deleteStatement = 
((java.sql.Connection) 
connection).prepareStatement(deleteSQL.toString());
[javac] 
^
[javac] 
/usr/local/src/postgresql-7.3rc1/src/interfaces/jdbc/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java:619: 
incompatible types
[javac] found   : java.sql.PreparedStatement
[javac] required: org.postgresql.jdbc2.PreparedStatement
[javac] insertStatement = 
((java.sql.Connection) 
connection).prepareStatement(insertSQL.toString());
[javac] 
^
[javac] 
/usr/local/src/postgresql-7.3rc1/src/interfaces/jdbc/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java:639: 
inconvertible types
[javac] found   : org.postgresql.jdbc2.PreparedStatement
[javac] required: org.postgresql.jdbc2.AbstractJdbc2Statement
[javac] long insertedOID = 
((AbstractJdbc2Statement) insertStatement).getLastOID();
[javac] 
^
[javac] 
/usr/local/src/postgresql-7.3rc1/src/interfaces/jdbc/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java:955: 
incompatible types
[javac] found   : java.sql.PreparedStatement
[javac] required: org.postgresql.jdbc2.PreparedStatement
[javac] selectStatement = 
((java.sql.Connection) 
connection).prepareStatement(selectSQL.toString());
[javac] 
^
[javac] 
/usr/local/src/postgresql-7.3rc1/src/interfaces/jdbc/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java:1038: 
incompatible types
[javac] found   : java.sql.PreparedStatement
[javac] required: org.postgresql.jdbc2.PreparedStatement
[javac] updateStatement = 
((java.sql.Connection) 
connection).prepareStatement(updateSQL.toString());
[javac] 
^
[javac] 
/usr/local/src/postgresql-7.3rc1/src/interfaces/jdbc/org/postgresql/jdbc2/AbstractJdbc2Statement.java:51: 
inconvertible types
[javac] found   : org.postgresql.jdbc2.AbstractJdbc2Statement
[javac] required: org.postgresql.jdbc2.Statement
[javac] 
((AbstractJdbc2ResultSet)result).setStatement((Statement)this);
[javac] 
^
[javac] 
/usr/local/src/postgresql-7.3rc1/src/interfaces/jdbc/org/postgresql/jdbc2/Array.java:49: 
inconvertible types
[javac] found   : org.postgresql.jdbc2.ResultSet
[javac] required: org.postgresql.jdbc2.AbstractJdbc2ResultSet
[javac] this.rawString = 
((AbstractJdbc2ResultSet)rs).getFixedString(idx);
[javac]   ^
[javac] 
/usr/local/src/postgresql-7.3rc1/src/interfaces/jdbc/org/postgresql/jdbc2/Jdbc2Connection.java:14: 
org.postgresql.jdbc2.Jdbc2Connection should be declared abstract; it 
does not define 
getResultSet(java.sql.Statement,org.postgresql.Field[],java.util.Vector,java.lang.String,int) 
in org.postgresql.jdbc1.AbstractJdbc1Connection
[javac] public class Jdbc2Connection extends 
org.postgresql.jdbc2.AbstractJdbc2Connection implements 
java.sql.Connection
[javac]^
[javac] 
/usr/local/src/postgresql-7.3rc1

Re: [BUGS] Bug #822: Condition on rule is not respected.

[Luis Mota]

I forgot to add details of instalation:

I'm running linux kernel 2.2.22 and postgres  PostgreSQL 7.2.1 on 
i686-pc-linux-gnu, compiled by GCC 2.96

lmota

[EMAIL PROTECTED] wrote:
Luís Mota ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
Condition on rule is not respected.

Long Description
I think I spoted a bug while developing a database. To better understand if this was really a bug, I developed a small example that I include further down.

The question is that I want to write a rule that inserts a record in a second table (table B) each time a record is inserted on a first table A, and vice-versa.

To do this, I wrote two insert rules. To avoid a dead-lock, I created a  boolean field which serves as guard to the insertion. Unfortunatly, I think that the condition I set up in the insert rules is not respected.

Thanks for any help, Luís Mota

Sample Code
CREATE TABLE num_int (id serial, valor int, dummy bool);
CREATE TABLE num_real (id serial, valor real, dummy bool);

CREATE RULE int_insert AS ON INSERT TO num_int WHERE NEW.dummy IS NULL 
DO 
INSERT INTO num_real (valor,dummy) SELECT NEW.valor,true;

CREATE RULE real_insert AS ON INSERT TO num_real WHERE NEW.dummy IS NULL 
DO
INSERT INTO num_int (valor,dummy) SELECT NEW.valor,true;

When I try to insert a record, e.g:
INSERT INTO num_int (valor,dummy) values (7);

I get the following error:
ERROR:  query rewritten 10 times, may contain cycles

Also, if I try the following setup:
CREATE TABLE num_int (id serial, valor int, dummy bool);
CREATE TABLE num_real (id serial, valor real, dummy bool);

CREATE RULE int_insert AS ON INSERT TO num_int WHERE NEW.dummy IS NULL 
DO 
INSERT INTO num_real (valor,dummy) SELECT NEW.valor,true;

CREATE RULE real_insert AS ON INSERT TO num_real WHERE NEW.dummy IS NULL 
DO
SELECT  NEW.valor, NEW.dummy 
	INTO tanga;

After an insertion in num_int, which is successful, if I try the following query:
SELECT * from tanga;
 valor 
---
(0 rows)

This means that this table was created, even it has no record. My conclusion is that the real_insert rule was fired.




No file was uploaded with this report


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

[BUGS] pg_dump/pg_restore

[Colin Stearman]

Hi,
 
2 possible bugs in pg_dump/pg_restore related to 
large objects.
 
1. Large objects dumped, deleted then restored 
do not retain their original OIDs.  Big problem as we reference their OIDs 
in tables.
2. The pg_restore command --list indicated no Blobs 
in the dump file even when there are.  For example:

  .
  .
  72; 46588445 TABLE DATA table_3da6183d8bb21 
  nobody73; 46588481 TABLE DATA table_3da625d622b72 nobody74; 46588517 
  TABLE DATA table_3da625f19cc95 nobody75; 0 BLOBS BLOBS 
   
This is version 7.2.3 and the pg_dump used -c -C -o 
-Fc -Z1 -b switches,  pg_restore used no switches (other than -d, of 
course).
 
Thanks,
Colin
-Colin 
StearmanPresidentAshdown Technologies119 E. Main St.Milford, MA 
01757 USATel: +1 508-478-1234Fax: +1 508-478-1244www.ashdowntech.com

[BUGS] PostgreSQL 7.3rc1: initdb fais with '-W' switch given in the command line.

[Adam Buraczewski]

Name: Adam Buraczewski
Email address   : [EMAIL PROTECTED]

System Configuration
-
  Architecture  : Intel Pentium II

  Operating System  : Linux 2.4.19, glibc 3.2.1 (i686-pc-linux-gnu)

  PostgreSQL version: PostgreSQL 7.3 RC1

  Compiler used : GCC 3.2.1

Description of the problem
--

Initdb fais with '-W' switch given in the command line.

This option enables DBA to set initial password for the superuser
account created during database cluster creation (usually this account
is named "postgres", "pgsql" or similar).  This is done inside initdb
script by issuing ALTER USER command and setting the password.  After
this, initdb checks if all necessary files (pg_pwd and pg_group) were
created.

This worked well under PostgreSQL 7.2.  However, PostgreSQL 7.3beta
and 7.3rc1 do not create "pg_group" file during this stage.  When
initdb checks for existance of this file, the test fails and initdb
gives up.

A way to repeat the problem
---

First compile PostgreSQL 7.3 RC1:

$ env CFLAGS='-O2 -march=i686' CXXFLAGS='-O2 -march=i686' LDFLAGS='-s' \
./configure --prefix=/usr/lib/pgsql7.3 --with-gnu-ld --enable-nls \
--with-java --with-pgport=54321
$ make
$ make check
$ su -c make install

and then:

$ mkdir /var/pgsql
$ chown postgres.postgres /var/pgsql
$ cd /var/pgsql
$ su postgres
$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/pgsql7.3/lib
$ export PATH=$PATH:/usr/lib/pgsql7.3/bin
$ export PGDATA=/var/pgsql
$ export PGLIB=/usr/lib/pgsql7.3/lib
$ initdb -W
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale C.

Fixing permissions on existing directory /var/pgsql... ok
creating directory /var/pgsql7.3rc1/base... ok
creating directory /var/pgsql7.3rc1/global... ok
creating directory /var/pgsql7.3rc1/pg_xlog... ok
creating directory /var/pgsql7.3rc1/pg_clog... ok
creating template1 database in /var/pgsql/base/1... ok
creating configuration files... ok
initializing pg_shadow... ok
Enter new superuser password: ***
Enter it again: 
setting password... 
The group file wasn't generated. Please report this problem.

initdb failed.

$ ls -l global/
total 108
-rw---1 postgres postgres 8192 Nov 24 18:26 1260
-rw---1 postgres postgres0 Nov 24 18:25 1261
-rw---1 postgres postgres 8192 Nov 24 18:25 1262
-rw---1 postgres postgres16384 Nov 24 18:25 16620
-rw---1 postgres postgres16384 Nov 24 18:25 16621
-rw---1 postgres postgres 8192 Nov 24 18:25 16625
-rw---1 postgres postgres 8192 Nov 24 18:25 16626
-rw---1 postgres postgres16384 Nov 24 18:26 16643
-rw---1 postgres postgres16384 Nov 24 18:26 16644
-rw---1 postgres postgres 8192 Nov 24 18:26 pg_control
-rw---1 postgres postgres   52 Nov 24 18:26 pg_pwd

If you know how this problem might be fixed, list the solution below:
-

This problem could be easily fixed by removing the part of initdb
script which checks for "pg_group" file existance.  However, I don't
think if this is a good solution, since someone added this check on
purpose.

-- 
Adam Buraczewski <[EMAIL PROTECTED]> * Linux registered user #165585
GCS/TW d- s-:+>+:- a- C+++() UL$ P++ L E++ W+ N++ o? K? w--
O M- V- PS+ !PE Y PGP+ t+ 5 X+ R tv- b+ DI? D G++ e+++> h r+>++ y?

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] BUG

[paolo manca]

Hi, i've installed Postgres 7.2.2, Tomcat 3.1 and 
JDBC postgres 7.2. I'm trying to connect to a db that i've create (psql test 
test). I
 received the following error:
psql: FATAL 1: IDENT authetication failde for use 
"test"
 
Can you help me?
Best regards
Paolo Manca

[BUGS] Invalid free/delete

[Joshua Moore-Oliva]

While debugging with valgrind, I always receive the following error
message.



==30439== Invalid free() / delete / delete[]
==30439==at 0x400448F9: free (vg_clientfuncs.c:180)
==30439==by 0x421136CD: (within /lib/i686/libc-2.2.5.so)
==30439==by 0x4207F852: (within /lib/i686/libc-2.2.5.so)
==30439==by 0x400451FC: vgPlain___libc_freeres_wrapper
(vg_clientfuncs.c:585)
==30439==by 0x4202BCC9: (within /lib/i686/libc-2.2.5.so)
==30439==by 0x42017592: (within /lib/i686/libc-2.2.5.so)
==30439==by 0x80491E1: (within
/home/chatgris/code/mastermailings/code/daemons/email_manager/email_manager.o)
==30439==Address 0x402544D0 is not stack'd, malloc'd or free'd

I compiled a program with -L/usr/local/pgsql/lib -lpq

and then ran it with valgrind to check for memory leaks.

unfortunately, I don't know enough about pg to really understand what
could be casuing this, but problems like this can easily lead to
infrequent segfaults =).

Josh.


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

pgsql-bugs@postgresql.org

[srihari]

hi,
i have been trying to get access postgres database from kylix..
i couldn't...
i think problem at installation itself..odbc driver is not eableing.

plz give me detaled steps with exaples...and possible errors...for geting 
access to postgres.
thanks &Regds
srihari

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [BUGS] vacumm error

[Rod Taylor]

On Fri, 2002-11-22 at 15:51, Stefanos Harhalakis wrote:
> I'm running postgresql 7.2.1 on linux.
> 
> I cannot run vacuumm on a table in a database i'm running for about 7 months.
> I get:
> 
> ERROR:  No one parent tuple was found

Your best bet, since you've crashed with fsync off, is to dump and
reload the database.  This should clean up any data issues you currently
have -- assuming pg_dump functions on it.

That said, 7.2.3 has several vacuum fixes, but I don't think they'll fix
your problem.

-- 
Rod Taylor <[EMAIL PROTECTED]>


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [BUGS] RULE: ON DELETE doesn't stack deletes

[Rod Taylor]

Confirmed this problem on cvs-tip.

Replacing the DO INSTEAD ( DELETE) with DO INSTEAD (INSERT...)
allows multiple insert statements which function fine using OLD.a_data
and OLD.b_data.

So it must be something else.


Could it be because once the DELETE FROM A has run the tuple no longer
exists in the view?


On Wed, 2002-11-20 at 10:49, Malcolm Hutty wrote:
> According to the manual you can stack multiple queries in a RULE:

> CREATE RULE R_DEL_AB AS
> ON DELETE TO V_AB
> DO INSTEAD
> (
> DELETE FROM A WHERE a_data=OLD.a_data;
> DELETE FROM B WHERE b_data=OLD.b_data;
> );

-- 
Rod Taylor <[EMAIL PROTECTED]>


---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [BUGS] RULE: ON DELETE doesn't stack deletes

[Stephan Szabo]

On Wed, 20 Nov 2002, Malcolm Hutty wrote:

> According to the manual you can stack multiple queries in a RULE:
>
> CREATE RULE name AS ON event
>  TO object [ WHERE condition ]
>  DO [ INSTEAD ] action
>
> where action can be:
>
> NOTHING
> |
> query
> |
> ( query ; query ... )
> |
> [ query ; query ... ]
>
>
> This seems to work provided 'query' is not "DELETE"; if it is, only
> the first one is executed.

I think it's something like:
delete from v_ab
 turns into something equivalent to the two statements (I don't know
what the actual form of the queries is however)
 delete from a where a_data=ANY(select a_data from v_ab);
 delete from b where b_data=ANY(select b_data from v_ab);

So when the second runs there is no matching rows (having already had all
the a rows deleted).


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] =?x-unknown?q?Re=3A_=5BBUGS=5D_Bug_#823=3A__upper=28=29_does?==?x-unknown?q?_not_handle_=E5=2C_=E4_and_=F6_correctly=2E?=

[Stephan Szabo]

On Tue, 26 Nov 2002 [EMAIL PROTECTED] wrote:

> Marcus Andersson ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> upper() does not handle å, ä and ö correctly.
>
> Long Description
> The function upper() just leaves the letters å, ä, and ö unmodified.
> It should replace them with Å, Ä and Ö respectively.
>
> PostgreSQL version 7.2.3 on Solaris.
>
> I am using encoding 7 (ISO 8859-1).

It's probably a locale issue.  What locale did you initdb in?


---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Re: [BUGS] PostgreSQL 7.3rc1: initdb fais with '-W' switch given in the command line.

[Adam Buraczewski]

On Sun, Nov 24, 2002 at 06:37:09PM +0100, Adam Buraczewski wrote:
> Initdb fais with '-W' switch given in the command line.

Never mind, someone else found the bug as well, it is already removed
in CVS tree.  :)

-- 
Adam Buraczewski <[EMAIL PROTECTED]> * Linux registered user #165585
GCS/TW d- s-:+>+:- a- C+++() UL$ P++ L E++ W+ N++ o? K? w--
O M- V- PS+ !PE Y PGP+ t+ 5 X+ R tv- b+ DI? D G++ e+++> h r+>++ y?

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [BUGS] MemoryContextAllc error.

[Stephan Szabo]

On Wed, 20 Nov 2002 [EMAIL PROTECTED] wrote:

> i was trying to back up db from the server.
> i found the error while i was trying to backup.
>
> bash$ /usr/local/pgsql/bin/pg_dumpall > db.out
>
> ERROR:  MemoryContextAlloc: invalid request size 4294967293

I believe this probably means that you have at least one broken
row in the table. You'll probably need to find the affected row and
remove it.  See if you can do a select * from the table (it'll
probably fail as well), and then use limit/offset to find the
affected row(s).



---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] A little bug in postgreSQL

[Baiju MP]

 
Sir,
 
We are using postgreSQL for two years for our 
projects.
It's fine and working well and meets all out 
requirements.
But one think I could find when comparing with 
other simple
databases is I am mentioning here . Hope your 
developing team 
will consider this also while releasing the new 
version.
 
At present the all other database, providing an 
option to set 
developers own order with the 
order  by  statement.
eg : SELECT ..
   FROM  
..
        ORDER BY 1 
like 'A%' like 'H%' like 'G%' like 'C%' 
 
Please try to add this feature also on next version 
.
 
Regards,
Baiju MP
 
\|/ 
|  ~  ~  | 
    
(-   0 0  -)    
--oOOo---(_)---oOOo--    
 
Baiju 
MP, 
iPath India (P) 
LtdG-358, 
Panampilly 
Nagar, 
Cochin - 
36  
oooO   
    
---( 
)-Oooo---    
    
\   (  ( 
)  
\_)   )  
/    
(_/

Re: [BUGS] Minor build nits in 7.3rc1

[Bruce Momjian]

Harris Peter wrote:
> Hi
> 
> 1)
> configure fails too easily if your libraries and include files are in a
> funny place. When you specify --prefix=/somewhere, maybe it should use "-L
> /somewhere/lib" and "-I/somewhere/include" by default when checking if
> things exist.
> Workaround: I had to add the options to LDFLAGS and CPPFLAGS myself to get
> readline noticed.

Yes, I have seen that happen too.  Did you use --with-includes and
--with-libs?  I have seen cases where the actual compile of the software
honors those flags, but the configure tests don't.  Is that what you are
seeing?  I think config.log will show you the actual tests.


> 2)
> The makefile contains many rm.  I usually like to alias rm="rm -i" for
> safety, so I had to answer (y/n) a lot of times.  Could the makefile please
> use rm -f?

That is a little extreme.  If we use -f, then you will have rm -if, and
I don't know how that is supposed to behave.  Also, if there is an issue
with the rm, I think most will want to see it rather than have -f ignore
it.

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

[BUGS] order by in for loop in plpgsql does not work

[Jean-Luc Lachance]

Well, I think I found why.

Because OID is included in the selected fields list, the order by fields
number are off by one.
I rewrote the query using the field numbers instead of field names and
the function ran as expected.
It is a work around, but any ALTER to the table will force me to rewrite
the field numbers.

Someone should look into this. I think it is a bug.

JLL


Jean-Luc Lachance wrote:
> 
> Any idea why when I call this function the record are not processed in
> the order requested?
> 
> JLL
> 
> P.S.
> 
> It would be nice if the syntax would allow me to write something like >>
> cur.seqno = seq
> and have the underlying record updated.
> 
> declare
> 
> cur record;
> seq int;
> exchangeno text;
> routeno text;
> 
> begin
> 
> exchangeno := '';
> routeno := '';
> 
> for cur in
> select oid, * from r order by exchangeno, routeno, street,
> municipality, parity desc, fromno for update
> loop
> if cur.exchangeno != exchangeno or cur.routeno != routeno
> then
> seq := 1;
> exchangeno := cur.exchangeno;
> routeno := cur.routeno;
> end if;
> update r set seqno = seq, route = routeno || trim( lpad( seq, 4, '0'))
> where oid = cur.oid;
> seq := seq + 1;
> end loop;
> 
> return 0;
> end;
> 
> ---(end of broadcast)---
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [BUGS] Minor build nits in 7.3rc1

[Peter Eisentraut]

Harris Peter writes:

> Workaround: I had to add the options to LDFLAGS and CPPFLAGS myself to get
> readline noticed.

As you should.

> The makefile contains many rm.  I usually like to alias rm="rm -i" for
> safety, so I had to answer (y/n) a lot of times.  Could the makefile please
> use rm -f?

It does.  Please provide details, in case a spot was missed.

-- 
Peter Eisentraut   [EMAIL PROTECTED]


---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [BUGS] Bug #823: upper() does not handle , and correctly.

[Tom Lane]

[EMAIL PROTECTED] writes:
> upper() does not handle å, ä and ö correctly.

Sounds like you didn't set your locale correctly --- this is not an
encoding issue, it is a locale issue.

regards, tom lane

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [BUGS] version for sun cobalt qube 3

[Tom Lane]

Weber Gerhard <[EMAIL PROTECTED]> writes:
> we have a cobalt qube 3 with an old version 6.5 of postgresql. we use
> postgresql 7.2.3 on other platforms like windows.
> what we have to do for installing the mentioned, newest version on our
> cobalt qube 3? wich version we hav to download? how to install  on it?

IIRC, the Qube system uses Postgres itself for storing system data.
You'd better talk to Sun about possible compatibility issues before
you try updating the instance that the system uses.

The path of greatest safety would be to leave the system's instance
alone, and build a separate newer-version DB that you run in parallel
with the old DB.

To do that, just configure with an installation directory and default
port number different from where the system DB lives.  Build, install,
initdb in a different directory from the system's, and you're set.

regards, tom lane

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [BUGS] RULE: ON DELETE doesn't stack deletes

[Tom Lane]

Rod Taylor <[EMAIL PROTECTED]> writes:
> Could it be because once the DELETE FROM A has run the tuple no longer
> exists in the view?

Precisely.  OLD is only a macro for the view, and the first delete
changes what's in the view ...

regards, tom lane

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]

Re: [BUGS] Can't start postmaster on Cygwin with local 'ja_JP.EUC

[Peter Eisentraut]

Tamotsu Ebina writes:

> ebina@HAYAMA02 /usr/local/pgsql/postgresql-7.3rc1
> $ FATAL:  invalid value for option 'LC_MESSAGES': 'ja_JP.EUC'

Set LC_MESSAGES to something that your system supports.  (Since Cygwin
doesn't have locale support anyway, you might as well unset the locale
environment variables.)

-- 
Peter Eisentraut   [EMAIL PROTECTED]


---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Re: [BUGS] vacumm error

[Tom Lane]

Stefanos Harhalakis <[EMAIL PROTECTED]> writes:
> I'm running postgresql 7.2.1 on linux.
> I cannot run vacuumm on a table in a database i'm running for about 7 months.
> I get:

> ERROR:  No one parent tuple was found

> I've found an older posting about that but the poster said that after 
> restarting it was fixed. In my case this is not true.

There is a known form of this problem that does not go away on restart.
I can't recall at the moment if it's fixed in 7.2.3 or not (been a long
day ...)  It is definitely fixed for 7.3 though.

If you don't want to update to 7.3 in the near future, I think there is
a workaround involving doing SELECT FOR UPDATE to clear out the bogus
state.  Check the pghackers archives from back around August for
details.

regards, tom lane

---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster

Re: [BUGS] Invalid free/delete

[Neil Conway]

On Mon, 2002-11-25 at 11:22, Joshua Moore-Oliva wrote:
> While debugging with valgrind, I always receive the following error
> message.
> 
> ==30439== Invalid free() / delete / delete[]
> ==30439==at 0x400448F9: free (vg_clientfuncs.c:180)
> ==30439==by 0x421136CD: (within /lib/i686/libc-2.2.5.so)
> ==30439==by 0x4207F852: (within /lib/i686/libc-2.2.5.so)
> ==30439==by 0x400451FC: vgPlain___libc_freeres_wrapper
> (vg_clientfuncs.c:585)
> ==30439==by 0x4202BCC9: (within /lib/i686/libc-2.2.5.so)
> ==30439==by 0x42017592: (within /lib/i686/libc-2.2.5.so)
> ==30439==by 0x80491E1: (within
> /home/chatgris/code/mastermailings/code/daemons/email_manager/email_manager.o)
> ==30439==Address 0x402544D0 is not stack'd, malloc'd or free'd

ISTM that indicates a problem in your application, not in libpq.

Cheers,

Neil

-- 
Neil Conway <[EMAIL PROTECTED]> || PGP Key ID: DB3C29FC




---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html

Re: [BUGS] A little bug in postgreSQL

[Neil Conway]

On Tue, 2002-11-26 at 13:35, Baiju MP wrote:
> At present the all other database, providing an option to set 
> developers own order with the order  by  statement.
> eg : SELECT ..
>FROM  ..
> ORDER BY 1 like 'A%' like 'H%' like 'G%' like 'C%' 

Can you elaborate on exactly what behavior you'd expect this to produce?
We already support this syntax:

[ ORDER BY expression [ ASC | DESC | USING operator ] [, ...] ]

Cheers,

Neil

-- 
Neil Conway <[EMAIL PROTECTED]> || PGP Key ID: DB3C29FC




---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [BUGS] Minor build nits in 7.3rc1

[Tom Lane]

Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Harris Peter writes:
>> Workaround: I had to add the options to LDFLAGS and CPPFLAGS myself to get
>> readline noticed.

> As you should.

I agree, --prefix should not have anything to do with --with-includes/libs.

>> The makefile contains many rm.  I usually like to alias rm="rm -i" for
>> safety, so I had to answer (y/n) a lot of times.  Could the makefile please
>> use rm -f?

> It does.  Please provide details, in case a spot was missed.

I alias "rm" to "rm -i" also, and I have never seen this happen.
I think Peter H. has got some configuration problem (perhaps he's
somehow overriding make's usual use of /bin/sh to execute commands?)

regards, tom lane

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

[BUGS] [SQL/BUGS] (possible) inconsistent behaviour of timestamp?

[Rison, Stuart]

Here's an "interesting" timestamp related postgreSQL quirk:

testdb2=# select "timestamp"('now');
 timestamp

 2002-11-26 13:47:12.454157
(1 row)

testdb2=# select 'now'::timestamp;
 timestamptz
--
 2002-11-26 13:47:34.88358+00
(1 row)

testdb2=# select timestamp 'now';
  timestamptz
---
 2002-11-26 13:47:47.701731+00
(1 row)

The first SELECT returns a 'timestamp', but the next two return a
'timestamptz' (presumably with timezone); is this inconsitent behaviour?

Cheers,

Stuart.
Royal Veterinary College
London, UK

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [BUGS] [SQL] [SQL/BUGS] (possible) inconsistent behaviour of timestamp?

[Tom Lane]

"Rison, Stuart" <[EMAIL PROTECTED]> writes:
> The first SELECT returns a 'timestamp', but the next two return a
> 'timestamptz' (presumably with timezone); is this inconsitent behaviour?

Yes.  It's a transitional behavior in 7.2: timestamp without any quotes
is translated by the parser to timestamptz (ie, timestamp with time
zone).  Quotes suppress the renaming, however.

We did that deliberately for one release to ease updating, because PG's
old "datetime" datatype corresponds to timestamptz, not timestamp-without-
time-zone.  As of 7.3 that renaming doesn't happen any more, and
undecorated timestamp means timestamp without time zone, per spec.

Confused yet?  I'm not sure that this update plan was really a great
idea, but we agreed to it a release or two back, and we're sticking to
it...

regards, tom lane

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly