Re: [BUGS] BUG #2631: database locking problem

2006-09-16 Thread Tom Lane
"Ross Elliott" <[EMAIL PROTECTED]> writes:
> So, what happened between 8.1.3 and 8.1.4 that may
> have affected locking?

Nothing that I know of.  Please provide a self-contained test case
(but are you sure this is not a PostGIS bug?) ...

regards, tom lane

---(end of broadcast)---
TIP 6: explain analyze is your friend


[BUGS] BUG #2631: database locking problem

2006-09-16 Thread Ross Elliott

The following bug has been logged online:

Bug reference:  2631
Logged by:  Ross Elliott
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system:   Red Hat  AS 4
Description:database locking problem
Details: 

I have a dataset of aprox 650 million rows that I load into 5 spatial
(PostGIS) tables using 9 client machines (via JDBC). On 8.1.3 this all works
fine but on 8.1.4 it will fail with just three clients loading the data. The
database will lock up, the process list shows the clients  performing an
INSERT, the postgres locks show each client having an exclusive row lock and
these locks seem to move about, that is it would seem to be working, except
that nothing is being inserted, I've left the system in this state for over
a day just to make sure. So, what happened between 8.1.3 and 8.1.4 that may
have affected locking?

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


Re: [BUGS] BUG #2629: libpq - Cannot deallocate prepared statement created with PQprepare()

2006-09-16 Thread Tom Lane
"Andy McCurdy" <[EMAIL PROTECTED]> writes:
> result = PQprepare(conn, "MyQuery", "select * from pg_stat_activity", 0,
> NULL);

I believe the above will result in preparing a statement named "MyQuery",
ie, no case-folding happens on the second argument of PQprepare, because
it never goes through the SQL parser.

> /* 
> THE FOLLOW PQEXEC() FAILS.  Error message says:  ERROR:  prepared statement
> "myquery" does not exist"
> */
> result = PQexec(conn, "DEALLOCATE MyQuery");

I think this would work:

result = PQexec(conn, "DEALLOCATE \"MyQuery\"");

regards, tom lane

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

   http://www.postgresql.org/docs/faq


Re: [BUGS] BUG #2629: libpq - Cannot deallocate prepared statement created with PQprepare()

2006-09-16 Thread Michael Fuhr
On Fri, Sep 15, 2006 at 07:39:32AM +, Andy McCurdy wrote:
> result = PQprepare(conn, "MyQuery", "select * from pg_stat_activity", 0,
> NULL);
> 
> /* 
> THE FOLLOW PQEXEC() FAILS.  Error message says:  ERROR:  prepared statement
> "myquery" does not exist"
> */
> result = PQexec(conn, "DEALLOCATE MyQuery");

You prepared a mixed-case identifier so you'll need to quote it in
SQL statements to preserve its case.  Unquoted identifiers are
folded to lowercase, as the error message shows.

result = PQexec(conn, "DEALLOCATE \"MyQuery\"");

See "Identifiers and Key Words" in the "SQL Syntax" chapter of the
documentation for more information about quoted identifiers.

http://www.postgresql.org/docs/8.1/interactive/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS

-- 
Michael Fuhr

---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings


Re: [BUGS] BUG #2630: Can't unpack

2006-09-16 Thread Magnus Hagander
> 
> Bug reference:  2630
> Logged by:  Alan Escreet
> Email address:  [EMAIL PROTECTED]
> PostgreSQL version: 8.1.4
> Operating system:   Windows
> Description:Can't unpack
> Details: 
> 
> I am unable to unpack the database from the tar.gz file. I 
> have tried all the suggested packages to do so from the gzip 
> website, but they were all unsuccessful. I have checked the 
> downloaded file's md5 checksum and it is ok. Is there an 
> error in the tar.gz file?
> Is there a differently packaged PostgreSQL that I can try 
> (i.e. a zip file)?
> It has taken me 3 hours so far trying to get the database out 
> of the box with no success...

If you're building from source, the tar package of msys should work just
fine, and you need msys anyway.

If you just want the binary installer, you are downloading the wrong
file - you'll want the ZIP archive at
http://www.postgresql.org/ftp/binary/v8.1.4/win32/.

//Magnus

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

   http://archives.postgresql.org


[BUGS] BUG #2630: Can't unpack

2006-09-16 Thread Alan Escreet

The following bug has been logged online:

Bug reference:  2630
Logged by:  Alan Escreet
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system:   Windows
Description:Can't unpack
Details: 

I am unable to unpack the database from the tar.gz file. I have tried all
the suggested packages to do so from the gzip website, but they were all
unsuccessful. I have checked the downloaded file's md5 checksum and it is
ok. Is there an error in the tar.gz file?
Is there a differently packaged PostgreSQL that I can try (i.e. a zip file)?
It has taken me 3 hours so far trying to get the database out of the box
with no success...

---(end of broadcast)---
TIP 1: 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] wrong behavior using to_char()

2006-09-16 Thread Jorge Godoy
"Euler Taveira de Oliveira" <[EMAIL PROTECTED]> writes:

> In the pt_BR locale, the thousand separator is "". So it should return

The thousands separator in pt_BR is ".".  

> 12345,670. Looking at the source, I saw that the test cases for locale

This should be "12.345,670". 



-- 
Jorge Godoy  <[EMAIL PROTECTED]>

---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
   choose an index scan if your joining column's datatypes do not
   match


[BUGS] Clarification : Postmaster crash

2006-09-16 Thread Lakshminarayanan Radhakrishan

Hi,

Postmaster is crashing in my system and following trace is recorded in 
the log file.

Can you please check and let me know the root cause of the crash ?

LOG:  database system was interrupted at 2006-09-13 13:28:51 CEST
LOG:  record with zero length at 0/B37888
LOG:  invalid primary checkpoint record
LOG:  record with zero length at 0/B37848
LOG:  invalid secondary checkpoint record
PANIC:  could not locate a valid checkpoint record
LOG:  startup process (PID 470) was terminated by signal 6
LOG:  aborting startup due to startup process failure

thanks & regards
Laks







---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
  choose an index scan if your joining column's datatypes do not
  match


[BUGS] BUG #2629: libpq - Cannot deallocate prepared statement created with PQprepare()

2006-09-16 Thread Andy McCurdy

The following bug has been logged online:

Bug reference:  2629
Logged by:  Andy McCurdy
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.1.4
Operating system:   Windows XP
Description:libpq - Cannot deallocate prepared statement created
with PQprepare()
Details: 

According to http://www.postgresql.org/docs/8.1/interactive/libpq-exec.html,
the last statement in the PQprepare() function description suggests that a
user can run the statement: "DEALLOCATE [statement name]" with PQexec() to
deallocate a statement prepared with PQprepare().  When trying to do this, I
consistently get the error message:

ERROR:  prepared statement "[statement name]" does not exist

Here's a snippet of code that illustrates what I am attempting to do:

int main()
{

PGconn* conn;
PGresult* result;

conn = PQsetdbLogin("localhost", "5432", NULL, NULL, "postgres", "postgres",
"postgres");

result = PQprepare(conn, "MyQuery", "select * from pg_stat_activity", 0,
NULL);

/* 
THE FOLLOW PQEXEC() FAILS.  Error message says:  ERROR:  prepared statement
"myquery" does not exist"
*/
result = PQexec(conn, "DEALLOCATE MyQuery");


result = PQexec(conn, "PREPARE MyQuery AS select * from pg_stat_activity");

/*
THIS WORKS
*/
result = PQexec(conn, "DEALLOCATE MyQuery");



return 0;
}

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


[BUGS] backup + restore fails

2006-09-16 Thread Schoenen, Holger
I have installed the new postgresql-8.1.msi on windows XP. 
All standard as proposed except: encoding UTF8 and locale Germany/german as
a service. (UTF8 seams to be important, the locale not?)

Using pgAdmin-III I have connected and created a new database. Optionally I
can create a table - same result. Analyse: no errors found.

Then: backup compressed and restore using pgAdminIII.
I will get the error: pg_restore: [archiver (db)] could not execute query:
ERROR:  invalid byte sequence for encoding "UTF8": 0xe46973
Command was: --
Why that???

In the backup or in the SQL-dump (see below) the are special german
"Umlaute" ("ä")
-- Started on 2006-09-15 14:56:51 Westeuropäische Normalzeit
This is only comment and I have no influence on it, but possibly the source
of the problem?

If I hit "ok" expecting to close the window the same happens again. I have
clipped the result here:

--- clipp ---
C:\Programme\PostgreSQL\8.1\bin\pg_restore.exe -i -h localhost -p 5432 -U
postgres -d ibv -v "C:\eclispace\ibv\ibv-site\tableN1.backup"
pg_restore: connecting to database for restore
pg_restore: [archiver (db)] Error while INITIALIZING:
pg_restore: [archiver (db)] could not execute query: ERROR:  invalid byte
sequence for encoding "UTF8": 0xe46973
Command was: --
-- PostgreSQL database dump
--

-- Started on 2006-09-15 13:16:16 Westeuropäische Normalzeit

SET client_encoding = 'UTF8';
pg_restore: creating SCHEMA public
pg_restore: creating COMMENT SCHEMA public
pg_restore: creating PROCEDURAL LANGUAGE plpgsql
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 249; 2612 16386 PROCEDURAL
LANGUAGE plpgsql 
pg_restore: [archiver (db)] could not execute query: ERROR:  language
"plpgsql" already exists
Command was: CREATE PROCEDURAL LANGUAGE plpgsql;
pg_restore: creating TABLE test
pg_restore: [archiver (db)] Error from TOC entry 1183; 1259 16404 TABLE test
postgres
pg_restore: [archiver (db)] could not execute query: ERROR:  relation "test"
already exists
Command was: CREATE TABLE test (
spalte character varying NOT NULL
);
pg_restore: restoring data for table "test"
pg_restore: creating CONSTRAINT test_pkey
pg_restore: [archiver (db)] Error from TOC entry 1506; 2606 16410 CONSTRAINT
test_pkey postgres
pg_restore: [archiver (db)] could not execute query: ERROR:  multiple
primary keys for table "test" are not allowed
Command was: ALTER TABLE ONLY test
ADD CONSTRAINT test_pkey PRIMARY KEY (spalte);
pg_restore: setting owner and privileges for SCHEMA public
pg_restore: setting owner and privileges for COMMENT SCHEMA public
pg_restore: setting owner and privileges for ACL public
pg_restore: setting owner and privileges for PROCEDURAL LANGUAGE plpgsql
pg_restore: setting owner and privileges for TABLE test
pg_restore: setting owner and privileges for CONSTRAINT test_pkey
WARNING: errors ignored on restore: 4

Prozess beendet mit Exitcode 1.
C:\Programme\PostgreSQL\8.1\bin\pg_restore.exe -i -h localhost -p 5432 -U
postgres -d ibv -v "C:\eclispace\ibv\ibv-site\tableN1.backup"
pg_restore: connecting to database for restore
pg_restore: [archiver (db)] Error while INITIALIZING:
pg_restore: [archiver (db)] could not execute query: ERROR:  invalid byte
sequence for encoding "UTF8": 0xe46973
Command was: --
-- PostgreSQL database dump
--

-- Started on 2006-09-15 13:16:16 Westeuropäische Normalzeit

SET client_encoding = 'UTF8';
pg_restore: creating SCHEMA public
pg_restore: creating COMMENT SCHEMA public
pg_restore: creating PROCEDURAL LANGUAGE plpgsql
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 249; 2612 16386 PROCEDURAL
LANGUAGE plpgsql 
pg_restore: [archiver (db)] could not execute query: ERROR:  language
"plpgsql" already exists
Command was: CREATE PROCEDURAL LANGUAGE plpgsql;
pg_restore: creating TABLE test
pg_restore: [archiver (db)] Error from TOC entry 1183; 1259 16404 TABLE test
postgres
pg_restore: [archiver (db)] could not execute query: ERROR:  relation "test"
already exists
Command was: CREATE TABLE test (
spalte character varying NOT NULL
);
pg_restore: restoring data for table "test"
pg_restore: creating CONSTRAINT test_pkey
pg_restore: [archiver (db)] Error from TOC entry 1506; 2606 16410 CONSTRAINT
test_pkey postgres
pg_restore: [archiver (db)] could not execute query: ERROR:  multiple
primary keys for table "test" are not allowed
Command was: ALTER TABLE ONLY test
ADD CONSTRAINT test_pkey PRIMARY KEY (spalte);
pg_restore: setting owner and privileges for SCHEMA public
pg_restore: setting owner and privileges for COMMENT SCHEMA public
pg_restore: setting owner and privileges for ACL public
pg_restore: setting owner and privileges for PROCEDURAL LANGUAGE plpgsql
pg_restore: setting owner and privileges for TABLE test
pg_restore: setting owner and privileges for CONSTRAINT test_pkey
WARNING: errors ignored on restore: 4

Prozess beendet mit Exitcode 1.
--- cli

[BUGS] BUG #2628: jdbc2

2006-09-16 Thread viniciusasousa

The following bug has been logged online:

Bug reference:  2628
Logged by:  viniciusasousa
Email address:  [EMAIL PROTECTED]
PostgreSQL version: 8.0
Operating system:   windows
Description:jdbc2
Details: 

I has problem:

org.postgresql.jdbc2.Jdbc2DatabaseMetaData.locatorsUpdateCopy()Z

---(end of broadcast)---
TIP 1: 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