>
> Hi,
>
> I was just installing postgres 7.1.2 on my linux mandrake 7.2
> system and the build and install went fine up to the point I
> had to run:
>
>initdb -D /usr/local/pgsql/data
>
> which segfaulted. I changed the permissions on /tmp to 777
> and
I have added documentation for code 209. Looks like there are other
undocumented ones. Should we document them all?
> John Summerfield writes:
>
> > I'm using 7.2devel from CVS, and as I've already reported, the documentation
>doesn't build.
>
> http://www.ca.postgresql.org/devel-corner/doc
Anonymous ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Backend crashes when using certain commands with SJIS encoded databases
Long Description
The problem seems to occur when using databases with SJIS encoding.
So far, I h
When adding an index to a (quite large, ~2 million rows) table
PostgreSQL continues to do sequential lookups until VACUUM ANALYZE is
run. Naturally performance is poor.
The CREATE INDEX statement takes considerable time.
Seen with 7.1.3 on Intel Linux (RedHat 7.0 & 7.1 and Solaris 2.6.
In the e
Can someone comment on this? The problem appears in current sources:
test=> INSERT INTO a VALUES ('infinity');
ERROR: Unrecognized date external representation 'infinity'
Is there a reason we support "infinity" in timestamp and not date?
> Dax Kelson ([EMAIL PROTECTED]) repor
Premysl Maly ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Integer overflow in pg_dump
Long Description
Talking about version pg_dump (7.1.3)
Well, it fails, when dumping databases indices (while dumping comment on indexes
