On Tue, Mar 01, 2011 at 01:20:43PM -0800, daveg wrote:
On Tue, Mar 01, 2011 at 12:00:54AM +0200, Heikki Linnakangas wrote:
On 28.02.2011 23:28, daveg wrote:
On Wed, Jan 12, 2011 at 10:46:14AM +0200, Heikki Linnakangas wrote:
We'll likely need to go back and forth a few times with various
Excerpts from daveg's message of mié mar 02 18:30:34 -0300 2011:
After a restart and vacuum of all dbs with no other activity things were
quiet for a couple hours and then we started seeing these PD_ALL_VISIBLE
messages again.
Going back through the logs we have been getting these since at
On Wed, Mar 02, 2011 at 06:45:13PM -0300, Alvaro Herrera wrote:
Excerpts from daveg's message of mié mar 02 18:30:34 -0300 2011:
After a restart and vacuum of all dbs with no other activity things were
quiet for a couple hours and then we started seeing these PD_ALL_VISIBLE
messages
On Wed, Mar 2, 2011 at 3:53 PM, daveg da...@sonic.net wrote:
Postgresql version is 8.4.4.
I don't see how this could be related, but since you're running on NFS,
maybe it is, somehow:
http://archives.postgresql.org/message-id/4d40ddb7.1010...@credativ.com
(for example what if the visibility
On Wed, Mar 02, 2011 at 04:20:24PM -0800, bricklen wrote:
On Wed, Mar 2, 2011 at 3:53 PM, daveg da...@sonic.net wrote:
Postgresql version is 8.4.4.
I don't see how this could be related, but since you're running on NFS,
maybe it is, somehow:
Hi
On Tue, Mar 1, 2011 at 11:00 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 28.02.2011 23:28, daveg wrote:
On Wed, Jan 12, 2011 at 10:46:14AM +0200, Heikki Linnakangas wrote:
We'll likely need to go back and forth a few times with various
debugging patches until
On Mon, Feb 28, 2011 at 07:43:39PM -0600, David Christensen wrote:
On Feb 28, 2011, at 3:28 PM, daveg wrote:
Anything new on this? I'm seeing at on one of my clients production boxes.
Also, what is the significance, ie what is the risk or damage potential if
this flag is set
On Tue, Mar 01, 2011 at 12:00:54AM +0200, Heikki Linnakangas wrote:
On 28.02.2011 23:28, daveg wrote:
On Wed, Jan 12, 2011 at 10:46:14AM +0200, Heikki Linnakangas wrote:
We'll likely need to go back and forth a few times with various
debugging patches until we get to the heart of this..
On 28.02.2011 23:28, daveg wrote:
On Wed, Jan 12, 2011 at 10:46:14AM +0200, Heikki Linnakangas wrote:
We'll likely need to go back and forth a few times with various
debugging patches until we get to the heart of this..
Anything new on this? I'm seeing at on one of my clients production
On Wed, Jan 12, 2011 at 10:46:14AM +0200, Heikki Linnakangas wrote:
On 12.01.2011 06:21, Fujii Masao wrote:
On Sat, Dec 25, 2010 at 2:09 PM, Maxim Bogukmaxim.bo...@gmail.com wrote:
While I trying create reproducible test case for BUG #5798 I
encountered very strange effect on two of my
On Feb 28, 2011, at 3:28 PM, daveg wrote:
On Wed, Jan 12, 2011 at 10:46:14AM +0200, Heikki Linnakangas wrote:
On 12.01.2011 06:21, Fujii Masao wrote:
On Sat, Dec 25, 2010 at 2:09 PM, Maxim Bogukmaxim.bo...@gmail.com wrote:
While I trying create reproducible test case for BUG #5798 I
On Tue, Mar 1, 2011 at 10:43 AM, David Christensen da...@endpoint.com wrote:
Was this cluster upgraded to 8.4.4 from 8.4.0? It sounds to me like a known
bug in 8.4.0 which was fixed by this commit:
commit 7fc7a7c4d082bfbd579f49e92b046dd51f1faf5f
Author: Tom Lane t...@sss.pgh.pa.us
Date:
On 12.01.2011 06:21, Fujii Masao wrote:
On Sat, Dec 25, 2010 at 2:09 PM, Maxim Bogukmaxim.bo...@gmail.com wrote:
While I trying create reproducible test case for BUG #5798 I
encountered very strange effect on two of my servers (both servers
have same hardware platform/OS (freebsd 7.2) and
On Sat, Dec 25, 2010 at 2:09 PM, Maxim Boguk maxim.bo...@gmail.com wrote:
While I trying create reproducible test case for BUG #5798 I
encountered very strange effect on two of my servers (both servers
have same hardware platform/OS (freebsd 7.2) and PostgreSQL 8.4.4).
Very simple test table
14 matches
Mail list logo