ilto:[EMAIL PROTECTED]
Sent: Thursday, August 30, 2007 4:07 PM
To: Nitin Verma
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] What kind of locks does vacuum process hold on the db?
On 8/30/07, Nitin Verma <[EMAIL PROTECTED]> wrote:
> > Why are you doing FULL vacuums? Is there
I have experimented vacuuming a table and running transaction on the same. It
works fine without pause injection. Is that because of MVCC?
akes a hard lock on a table.
That means Table Level AccessExclusiveLock, right?
-Original Message-
From: Scott Marlowe [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 30, 2007 10:29 AM
To: Nitin Verma
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] What kind of locks does vacuum
What kind of locks does it hold on the db? Table level / Row level /
AccessExclusiveLock ?
Is there a document that details vacuum process, and its internals?
Use case: I am doing a vacuum {all full analyze} on a postgres 8.1 hosting
two user databases. For this I am using ${pg-home}/bin/vacuumdb
/www.postgresql.org/docs/7.3/static/release-7-3-5.html
* Force zero_damaged_pages to be on during recovery from WAL
Is this related to XLogFlush problem?
-Original Message-
From: Scott Marlowe [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 9:26 PM
To: Nitin Verma
Cc: pgsql
me on a lower risk of getting in
this situation?
-Original Message-
From: Alvaro Herrera [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 8:59 PM
To: Nitin Verma
Cc: Tom Lane; [EMAIL PROTECTED]
Subject: Re: [GENERAL] ERROR: XLogFlush: request
Nitin Verma wrote:
> Thanx Tom, any
y use of or Is it safe to restart postmaster at this time?
What all should be done when this happened? Any suggestions.
=
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 8:18 PM
To: Nitin Verma
Cc: [EMAIL PROTECTED]
Subject: Re: [G
Hi All,
xlog.c code from version we use (7.3.2)
/*
* If we still haven't flushed to the request point then we have a
* problem; most likely, the requested flush point is past end of
* XLOG. This has been seen to occur when a disk page has a corrupted
*
java.sql.SQLException: ERROR: XLogFlush: request
0/240169BC is not satisfied --- flushed only to 0/23FFC01C
This error I was in the logs of a java process that was failing to get some
data. But using psql I was able to connect and query all the data. Thus this
may indicate some connection / state
Thanx Scott and Michael
-Original Message-
From: Michael Fuhr [mailto:[EMAIL PROTECTED]
Sent: Monday, June 26, 2006 9:18 PM
To: Nitin Verma
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] initlocation on 8.0+
On Mon, Jun 26, 2006 at 08:31:22AM -0700, Nitin Verma wrote:
> I
supported.
Regards,
Nitin Verma
---(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
0002
Looks like if a WAL file is created even vacuum can't reclaim the space. Is
that the root cause behind DB bloating with 7.3.2?
-Original Message-
From: Richard Huxton [mailto:[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 6:29 PM
To: Nitin Verma
Cc: pgsql-general@postgresq
Thanx so much which would really help
-Original Message-
From: Richard Huxton [mailto:[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 6:29 PM
To: Nitin Verma
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] VACUUMing sometimes increasing database size /
sometimes
Nitin Verma wrote
nges between 7.3 and 8.1,
may be release by release?
-Original Message-
From: Florian G. Pflug [mailto:[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 4:48 PM
To: Douglas McNaught
Cc: Nitin Verma; Jim Nasby; pgsql-general@postgresql.org
Subject: Re: [GENERAL] VACUUMing sometimes increasing d
te problem in export
and import across versions may hit. So please let me know all the do's and
don'ts... or the pointers to those.
-Original Message-
From: Jim Nasby [mailto:[EMAIL PROTECTED]
Sent: Friday, June 16, 2006 1:54 AM
To: Florian G.Pflug
Cc: Nitin Verma; pgsql-ge
Were these bugs fixed by 7.3.2, if not what version should I look for?
http://archives.postgresql.org/pgsql-admin/2001-06/msg5.php
http://archives.postgresql.org/pgsql-hackers/2000-04/msg00083.php
It would be gr8 if can myself look into bug list next time before asking
questions, any URL?
-
Is there a workaround for any of these?
-Original Message-
From: Nitin Verma
Sent: Thursday, June 15, 2006 11:03 PM
To: pgsql-general@postgresql.org
Subject: VACUUMing sometimes increasing database size / sometimes crashing it
Were these bugs fixed by 7.3.2, if not what version should
17 matches
Mail list logo
