Weird problem in 8.0.0

From: Devrim GUNDUZ <devrim(at)gunduz(dot)org>
To: PostgreSQL Mailing Lists-General <pgsql-general(at)postgresql(dot)org>
Subject: Weird problem in 8.0.0
Date: 2005-01-24 06:32:42
Message-ID: Pine.LNX.4.61.0501240824020.2042@emo.org.tr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I've just upgraded two servers to 8.0.0, using PGDG RPMs.

One of them is working well; however I'm experiencing problems in the
other one.

I first thought that this was a VACUMM issue; but then I saw that I can't
execute any command.

First case: Connected to template1 using psql and ran VACUMM. Here is the
log output (debug 5) (same thing happens when I run vacuumdb from the
command line)

=============================================================================
<[unknown][unknown]%t>LOG: connection received: host=[local] port=
<%t>DEBUG: forked new backend, pid=3104 socket=7
<postgrestemplate1%tauthentication>DEBUG: received password packet
<postgrestemplate1%tauthentication>LOG: connection authorized:
user=postgres database=template1
<postgrestemplate1%tauthentication>DEBUG: postmaster child[3104]:
starting with (
<postgrestemplate1%tauthentication>DEBUG: postgres
<postgrestemplate1%tauthentication>DEBUG: -v196608
<postgrestemplate1%tauthentication>DEBUG: -p
<postgrestemplate1%tauthentication>DEBUG: template1
<postgrestemplate1%tauthentication>DEBUG: )
<postgrestemplate1%tstartup>DEBUG: InitPostgres
<postgrestemplate1%tstartup>DEBUG: StartTransaction
<postgrestemplate1%tstartup>DEBUG: name: unnamed; blockState:
DEFAULT; state: INPROGR, xid/subid/cid: 4341/1/0, nestlvl: 1, children: <>
<postgrestemplate1%tstartup>DEBUG: CommitTransaction
<postgrestemplate1%tstartup>DEBUG: name: unnamed; blockState:
STARTED; state: INPROGR, xid/subid/cid: 4341/1/0, nestlvl: 1, children: <>
<postgrestemplate1%tidle>DEBUG: StartTransactionCommand
<postgrestemplate1%tidle>STATEMENT: VACUUM ;
<postgrestemplate1%tidle>DEBUG: StartTransaction
<postgrestemplate1%tidle>STATEMENT: VACUUM ;
<postgrestemplate1%tidle>DEBUG: name: unnamed; blockState: DEFAULT;
state: INPROGR, xid/subid/cid: 4342/1/0, nestlvl: 1, children: <>
<postgrestemplate1%tidle>STATEMENT: VACUUM ;
<postgrestemplate1%tidle>LOG: statement: VACUUM ;
<postgrestemplate1%tidle>STATEMENT: VACUUM ;
<postgrestemplate1%tVACUUM>DEBUG: ProcessUtility
<postgrestemplate1%tVACUUM>STATEMENT: VACUUM ;
<postgrestemplate1%tVACUUM>DEBUG: CommitTransaction
<postgrestemplate1%tVACUUM>STATEMENT: VACUUM ;
<postgrestemplate1%tVACUUM>DEBUG: name: unnamed; blockState:
STARTED; state: INPROGR, xid/subid/cid: 4342/1/0, nestlvl: 1, children: <>
<postgrestemplate1%tVACUUM>STATEMENT: VACUUM ;
<postgrestemplate1%tVACUUM>DEBUG: StartTransaction
<postgrestemplate1%tVACUUM>STATEMENT: VACUUM ;
<postgrestemplate1%tVACUUM>DEBUG: name: unnamed; blockState:
DEFAULT; state: INPROGR, xid/subid/cid: 4343/1/0, nestlvl: 1, children: <>
<postgrestemplate1%tVACUUM>STATEMENT: VACUUM ;
<postgrestemplate1%tVACUUM>DEBUG: vacuuming
"information_schema.sql_packages"
<postgrestemplate1%tVACUUM>STATEMENT: VACUUM ;
<postgrestemplate1%tVACUUM>ERROR: canceling query due to user request
<postgrestemplate1%tVACUUM>STATEMENT: VACUUM ;
=============================================================================

Now, second case:

template1=# \c proftpd
You are now connected to database "proftpd".
proftpd=# SELECT passwd FROM users WHERE userid='istanbul';
ERROR: canceling query due to user request

And the log shows:

=============================================================================
<postgresproftpd%tidle>DEBUG: StartTransactionCommand
<postgresproftpd%tidle>STATEMENT: SELECT passwd FROM users WHERE
userid='istanbul';
<postgresproftpd%tidle>DEBUG: StartTransaction
<postgresproftpd%tidle>STATEMENT: SELECT passwd FROM users WHERE
userid='istanbul';
<postgresproftpd%tidle>DEBUG: name: unnamed; blockState: DEFAULT;
state: INPROGR, xid/subid/cid: 4347/1/0, nestlvl: 1, children: <>
<postgresproftpd%tidle>STATEMENT: SELECT passwd FROM users WHERE
userid='istanbul';
<postgresproftpd%tidle>LOG: statement: SELECT passwd FROM users WHERE
userid='istanbul';
<postgresproftpd%tidle>STATEMENT: SELECT passwd FROM users WHERE
userid='istanbul';
<postgresproftpd%tSELECT>ERROR: canceling query due to user request
<postgresproftpd%tSELECT>STATEMENT: SELECT passwd FROM users WHERE
userid='istanbul';
<postgresproftpd%tidle>DEBUG: proc_exit(0)
<postgresproftpd%tidle>DEBUG: shmem_exit(0)
=============================================================================

What might be the problem? The upgrade process was done as usual...

Regards,

- --
Devrim GUNDUZ
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.tdmsoft.com http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFB9JaLtl86P3SPfQ4RAgwaAKCfupu287wiCGZntn6+WZmyg8QSBACgp8VO
i/6uRBjyMDdPcFIXCrlP2E8=
=dSc+
-----END PGP SIGNATURE-----

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ralph van Etten 2005-01-24 06:40:42 Re: serialization errors when inserting new records
Previous Message Niederland 2005-01-24 06:14:27 Re: pg_restore