The following bug has been logged online:
Bug reference: 1011
Logged by: Pawel Rutkowski
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: FreeBSD rsc.pl 4.9-STABLE FreeBSD 4.9-STABLE #22: Tue Dec 2
20:31:00 CET 2003
Description:Explain anal
Lewis Foti wrote:
> Further to my original message I realise that the problem was due to
> the text of the rule still referring to columns, src_section_id and
> dst_section_id by their original names, parent_section_id and
> child_section_id respectively. So the nature of the bug changes to
> that
Lewis Foti wrote:
> I have a schema which includes one table with a CHECK constraint.
> After the schema is dumped (with pg_dump) as ascii text attempts to
> recreate it using the psql -f command cause this one
> table, called navigaion, to fail to create. This is using postgresql
> 7.3.3 on Redha
Lauris Buk¨is wrote:
> I have PostgreSQL 7.3.2 on Mandrake 9.1.
> functions lower and upper doesn't convert UTF8 char cases... it just
> leave them as thay are. Atleast I have problems with latvian and
> russian letters. Database charset is set to UNICODE.
Yes, next time please search the archives
I have PostgreSQL 7.3.2 on Mandrake 9.1.
functions lower and upper doesn't convert UTF8 char cases... it just
leave them as thay are. Atleast I have problems with latvian and russian
letters. Database charset is set to UNICODE. Where is the problem and
what I should do?
Lauris
Hi
I have a schema
which includes one table with a CHECK constraint. After the schema is dumped
(with pg_dump) as ascii text attempts to recreate it using the psql -f
command cause this one table, called navigaion, to fail to
create. This is using postgresql 7.3.3 on Redhat 9.0. The frag
Further to my original message I realise that the problem was due to the
text of the rule still referring to columns, src_section_id and
dst_section_id by their original names, parent_section_id and
child_section_id respectively. So the nature of the bug changes to that
pg_dump does not correctly e
Dear List,
PostgreSQL 7.4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.1 (Mandrake
Linux 9.2 3.3.1-2mdk)
psqlodbc versions: 07_03_0100 & 07_03_0200
I've found a minor bug whilst using psqlodbc to connect to PostgreSQL. I have
found that if you set in postgresql.conf:
client_min_messag
The following bug has been logged online:
Bug reference: 1010
Logged by: Jeff Davis
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Linux, Mac OS X 10.3
Description:format_type errors oin formatting type interval.
Details:
head=# select ve
The following bug has been logged online:
Bug reference: 1009
Logged by: Christopher Hodson
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: freebsd 5.2
Description:ERROR: could not open segment 1 of relation...
Details:
I have a script th
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> But if I read SQL99 correctly, only referencing not referenced
> >> columns are supposed to be shown.
> >
> > It is supposed to show the referenced (primary key) columns.
>
> [ reads spec more carefully... ] Ye
POSTGRESQL BUG REPORT TEMPLATE
Your name : Michael Fuhr
Your email address : [EMAIL PROTECTED]
Syst
12 matches
Mail list logo