[ cc'ing to pgsql-performance because of performance issue for hash indexes ]
"Balazs Nagy" <[EMAIL PROTECTED]> writes:
> Database table size: ~60 million rows
> Field to index: varchar 127
> CREATE INDEX ... USING hash ...
> fails with a file not found error (psql in verbose mode):
> ERROR: 5
"Basil Evseenko" <[EMAIL PROTECTED]> writes:
> So pg_catalog.pg_get_serial_sequence return garbage: index name vs sequence
> name
Fixed, thanks for the report!
regards, tom lane
---(end of broadcast)---
TIP 1: if posting/rea
"Stephen haberman" <[EMAIL PROTECTED]> writes:
> Just tried postgresql 8.2 beta 3 and it is missing a patch I had sent to
> pgsql-patches after trying 8.2 beta 2 a few weeks ago.
Hm, there is no such message in the archives.
> The information_schema `position_in_unique_constraint` is broken when
"Dennis" <[EMAIL PROTECTED]> writes:
> PostgreSQL version: 8.1.5
> contrib\pgxml.sql has reference to xml_is_well_formed function.
Not in 8.1 there isn't. Sounds like you are trying to use an 8.2 beta
sql script with an 8.1 library.
regards, tom lane
---
The following bug has been logged online:
Bug reference: 2752
Logged by: Denis
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.5
Operating system: Gentoo 2006.1 server x86
Description:Website bug
Details:
Don't know where to file this bug, but when I submit
The following bug has been logged online:
Bug reference: 2751
Logged by: Dennis
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.5
Operating system: Gentoo 2006.1 server x86
Description:contrib\pgxml.sql
Details:
contrib\pgxml.sql has reference to xml_is_wel
On Wed, 8 Nov 2006, David Green wrote:
the JDBC driver does not handle setNull for boolean types.
the switch statement in setNull should be expanded with a case that
checks for Types.BOOLEAN
The JDBC2 driver does not handle Types.BOOLEAN because that was added in
JDBC3. See org.postgresq
