Skip site navigation (1) Skip section navigation (2)

Re: Hot standby and b-tree killed items

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hot standby and b-tree killed items
Date: 2008-12-20 20:07:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Gregory Stark wrote:
> A vacuum being replayed -- even in a different database -- could trigger the
> error. Or with the btree split issue, a data load -- again even in a different
> database -- would be quite likely cause your SELECT to be killed.

Hmm, I wonder if we should/could track the "latestRemovedXid" separately 
for each database. There's no reason why we need to kill a read-only 
query in database X when a table in database Y is vacuumed.

   Heikki Linnakangas

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2008-12-20 21:35:39
Subject: Re: dblink vs SQL/MED
Previous:From: Magnus HaganderDate: 2008-12-20 19:08:00
Subject: Re: [COMMITTERS] pgsql: Append major version number and for libraries soname major

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group