From: | Bruce McAlister <bruce(dot)mcalister(at)blueface(dot)ie> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Subject: | Re: AutoVacuum Behaviour Question |
Date: | 2007-06-28 09:33:58 |
Message-ID: | 46838086.2070505@blueface.ie |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Martijn van Oosterhout wrote:
> All the values here look OK, except one:
>
> On Thu, Jun 28, 2007 at 07:50:36AM +0100, Bruce McAlister wrote:
>> blueface-crm=# select oid, relfrozenxid from pg_class where relkind in
>> ('r', 't');
>> oid | relfrozenxid
>> ---------+--------------
>> 2570051 | 2947120794
>
> Whatever this table is, the freeze XID isn't getting updated for some
> reason...
>
> Have a nice day,
This looks like a temporary relation,
temp4295 | 2947120794
Is there a way we can manually force these to update?
Which brings me onto a possibly related question. I've noticed that in
this particular database, that there are temporary tables that are
created. I'm not 100% sure how/why these temporary tables are being
created, but I do assume that it must be by some sort of SQL query that
runs against the database. How does postgresql handle these temporary
tables, i mean, if a temporary table is created by some sql query, is it
up to the user performing the query to remove the temporary table
afterwards, or does postgresql automagically remove the temporary table
when the query completes?
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Hertroys | 2007-06-28 09:40:45 | Re: a JOIN on same table, but 'slided over' |
Previous Message | Rafal Pietrak | 2007-06-28 08:44:46 | Re: a JOIN on same table, but 'slided over' |
From | Date | Subject | |
---|---|---|---|
Next Message | Alban Hertroys | 2007-06-28 09:46:31 | Re: AutoVacuum Behaviour Question |
Previous Message | Michael Enke | 2007-06-28 08:48:30 | Re: self defined data type "with limit"? |