Re: [BUGS] bug in information_schema?

eless for some kinds of queries, like you have shown. However, I don't believe that schema-unique constraint names will be an option any time soon, due to backwards compatibility :-( -- Greetings from Troels Arvin, Copenhagen, Denmark ---(end of broadcast)

Re: [BUGS] BUG #1290: Default value and ALTER...TYPE

ied for - CREATE TABLE ... - ALTER TABLE ... ALTER COLUMN ... SET DEFAULT... - ALTER TABLE ... ALTER COLUMN ... TYPE... - CREATE DOMAIN ... -- Greetings from Troels Arvin, Copenhagen, Denmark ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster

Re: [BUGS] 7.4: CHAR padding inconsistency

about not testing this before 7.4 went gold, but I believe that this is a bug which should be corrected before too much confusion is created. Reference 1: An interesting one is this one: http://article.gmane.org/gmane.comp.db.postgresql.devel.general/10958/match=char+padding -- Gree

[BUGS] 7.4: CHAR padding inconsistency

6 SELECT CHARACTER_LENGTH(col) < CHARACTER_LENGTH(col||'hey') from chartest; ?column? -- f The last two results are horrifying, in my opinion, especially when you consider them in concert: Concatenating a value with another value decreases its length... -- G

Re: [BUGS] RC2 refuses to build if --infodir=foo is set

On Wed, 12 Nov 2003 23:13:38 -0500, Bruce Momjian wrote: > We don't have any .info documentation. Why should the option work? Why should it be displayed when "./configure --help" is run, then? -- Greetings from Troels Arvin, Copenhagen, Denmark --

[BUGS] RC2 refuses to build if --infodir=foo is set

Hello, RC2 will not build on my Red Hat 8 server if a "infodir=something" is added to the "./configure" command. - Even though the option is mentioned when doing "./configure --help". For various reasons, this makes PostgreSQL a bit more difficult to build as an R

[BUGS] Non-standard TIMESTAMP WITH TIME ZONE literal handling

ESTAMP-like literal parsing. Furthermore, as Oracle behaves as Melton+Simon describes, subtle, but potentially nasty portability problems can be imagined, hurting people porting to/from Oracle. -- Greetings from Troels Arvin, Copenhagen, Denmark ---(end of broadcas

[BUGS] Transactions and exceptions; trailing spaces in byteas

Hello, At http://ldbc.sourceforge.net/html/databases.html (see bottom of the page), two problems in PostgreSQL are mentioned. To me, it seems that the author is right: PostgreSQL's handling of exceptions in transactions and trailing spaces in BYTEAs are buggy. -- Greetings from Troels

[BUGS] pg_dump handling of trim()

nsider the above a (minor) bug. -- Greetings from Troels Arvin, Copenhagen, Denmark ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])