Cornelia Boenigk wrote:
Hi Ragnar
could not duplicate this.
I also cannot reproduce the hanging VACUUM FULL. The problem remains
thet the dead tuples cannot be vemoved.
[snip]
I am interested in this. As one database cannot talk to another database
in a transactional way a long running
Hi Ragnar
could not duplicate this.
I also cannot reproduce the hanging VACUUM FULL.
The problem remains thet the dead tuples cannot be vemoved.
dummy1=# vacuum full;
VACUUM
dummy1=# SELECT relpages, reltuples FROM pg_class WHERE relname ='dummy1';
-[ RECORD 1 ]-
relpages | 997
reltupl
On fim, 2006-12-07 at 20:04 +0100, Cornelia Boenigk wrote:
> Sorry, i was out
>
> [ snip demonstration of blocked vacuum full]
> running on pg 8.1.4 on Fedora 5
could not duplicate this.
can you show us the contents of pg_locks and
pg_stat_activity while the VACUUM is blocked?
gnari
---
Hi
Sorry, i was out
The first try was:
create database dummy1;
create table dummy ... and filled with 500 records
create database dummy2;
create table dummy ... and filled with 500 records
connecting to dummy1, opening a transaction and issued an update
begin;
update dummy set f1='achterbah
Bill Moran <[EMAIL PROTECTED]> writes:
>> [EMAIL PROTECTED] ~]# ps axw|grep postgres
>> 1746 ?S 0:00 postgres: writer process
>> 1747 ?S 0:00 postgres: stats buffer process
>> 1748 ?S 0:00 postgres: stats collector process
>> 2106 pts/1S 0:00 su postg
In response to Tom Lane <[EMAIL PROTECTED]>:
> Bill Moran <[EMAIL PROTECTED]> writes:
> > In response to Alvaro Herrera <[EMAIL PROTECTED]>:
> >> Of course they are able to complete, but the point is that they would
> >> not remove the tuples that would be visible to that idle open
> >> transactio
On fim, 2006-12-07 at 11:28 -0500, Tom Lane wrote:
> Bill Moran <[EMAIL PROTECTED]> writes:
> > In response to Alvaro Herrera <[EMAIL PROTECTED]>:
> >> Of course they are able to complete, but the point is that they would
> >> not remove the tuples that would be visible to that idle open
> >> trans
Bill Moran <[EMAIL PROTECTED]> writes:
> In response to Alvaro Herrera <[EMAIL PROTECTED]>:
>> Of course they are able to complete, but the point is that they would
>> not remove the tuples that would be visible to that idle open
>> transaction.
> I would expect that, but the OP claimed that vacuu
In response to Alvaro Herrera <[EMAIL PROTECTED]>:
> Bill Moran wrote:
> > In response to Christopher Browne <[EMAIL PROTECTED]>:
> > > Oops! [EMAIL PROTECTED] (Cornelia Boenigk) was seen spray-painting on a
> > > wall:
> > > > Hi all
> > > >
> > > > If I have a running transaction in database1 a
Bill Moran wrote:
> In response to Christopher Browne <[EMAIL PROTECTED]>:
> > Oops! [EMAIL PROTECTED] (Cornelia Boenigk) was seen spray-painting on a
> > wall:
> > > Hi all
> > >
> > > If I have a running transaction in database1 and try to vacuum
> > > database2 but the dead tuples in database2
In response to Christopher Browne <[EMAIL PROTECTED]>:
> Oops! [EMAIL PROTECTED] (Cornelia Boenigk) was seen spray-painting on a wall:
> > Hi all
> >
> > If I have a running transaction in database1 and try to vacuum
> > database2 but the dead tuples in database2 cannot be removed.
> >
> > INFO: v
Oops! [EMAIL PROTECTED] (Cornelia Boenigk) was seen spray-painting on a wall:
> Hi all
>
> If I have a running transaction in database1 and try to vacuum
> database2 but the dead tuples in database2 cannot be removed.
>
> INFO: vacuuming "public.dummy1"
> INFO: "dummy1": found 0 removable, 14
Cornelia Boenigk <[EMAIL PROTECTED]> wrote:
>
> Hi Bill
>
> > I don't believe that's the reason. AFAIK, activity in one database
> > will never block activity in another.
>
> This way I read the documentation.
psql -U pgsql db2
Welcome to psql 8.2.0, the PostgreSQL interactive terminal.
Type
Hi
as soon as I committed the open transaction the hangig vacuum full
completed and the table was vacuumed:
regards
Conni
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Hi Bill
> I don't believe that's the reason. AFAIK, activity in one database
> will never block activity in another.
This way I read the documentation.
> I would suspect that you haven't vacuumed this database in a long time,
I created both databases one hour ago for just testing this behavio
Cornelia Boenigk <[EMAIL PROTECTED]> wrote:
>
> Hi all
>
> If I have a running transaction in database1 and try to vacuum database2
> but the dead tuples in database2 cannot be removed.
>
> INFO: vacuuming "public.dummy1"
> INFO: "dummy1": found 0 removable, 14 nonremovable row versions in
Hi all
If I have a running transaction in database1 and try to vacuum database2
but the dead tuples in database2 cannot be removed.
INFO: vacuuming "public.dummy1"
INFO: "dummy1": found 0 removable, 14 nonremovable row versions in
1341 pages
DETAIL: 135000 dead row versions cannot be
17 matches
Mail list logo
