"Rajesh Kumar Mallah" <[EMAIL PROTECTED]> writes:
> This issue has been posted before also but this time i wanted
> to know, if it is possible to know what statements have been
> executed by the backend in the same transaction which is currently
> idle. this can probably help us in identifying the
This may help you...
http://archives.postgresql.org/pgsql-announce/2006-01/msg7.php
- Original Message -
From: Rajesh Kumar Mallah
To: Lista Postgres
Sent: Monday, January 22, 2007 9:55 AM
Subject: [ADMIN] Getting previous statements executed a backend currenly in
an i
On 1/22/07, Umesh Shastry <[EMAIL PROTECTED]> wrote:
This may help you...
thanks for reply.
but thats for slow queries. Blocked queries are different
regds
mallah.
http://archives.postgresql.org/pgsql-announce/2006-01/msg7.php
---(end of broadcast)
Dear Friends,
Due to some bug(s) in our apps , in a mod_perl environment
many backend remain in in transaction state. This
backends sometimes block other statements in batch
processes which in turn blocks access to some production
tables.
This issue has been posted before also but this time i w
ABC <[EMAIL PROTECTED]> writes:
> FATAL: database files are incompatible with server
> DETAIL: The database cluster was initialized with PG_CONTROL_VERSION 0, but
> the server was compiled with PG_CONTROL_VERSION 72.
It looks to me like something has happened to your pg_control file :-(
What do
AFAIK PG_CONTROL_VERSION should never be 0, so it sounds like your
hardware corrupted something. IF you're doing all of this on the *same
hardware and OS*, I suggest the following:
Make a copy of the data directory (ie: cp -R)
With the 7.2 initdb, create a new cluster somewhere (doesn't matter
whe
On Fri, Jan 19, 2007 at 03:45:18PM -0600, Peter Koczan wrote:
> I'm upgrading our Postgres installation from 7.4 to 8.2 (I know, I know, but
> we've been busy). The biggest thing to change will be our user/group
> management scripts, as they directly modify pg_shadow and pg_group. Beyond
> being po
On 1/21/07, ABC <[EMAIL PROTECTED]> wrote:
We are facing a probelm and its very urgent to sort it out. Please Help.
The database server unexpectedly shutdown down due to power failure. On
reboot, Postgresql server fails to start giving following Error:
-
We are facing a probelm and its very urgent to sort it out. Please Help.
The database server unexpectedly shutdown down due to power failure. On reboot,
Postgresql server fails to start giving following Error:
We are facing a probelm and its very urgent to sort it out. Please Help.
The database server unexpectedly shutdown down due to power failure. On reboot,
Postgresql server fails to start giving following Error:
---
10 matches
Mail list logo