Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> No, it isn't. Please add a TODO item about it:
> * Prevent long-lived temp tables from causing frozen-Xid advancement
> starvation
> >>
> > Jeff Amiel wrote:
> >> Can somebody explain this one to me? because of our aud
Alvaro Herrera <[EMAIL PROTECTED]> writes:
No, it isn't. Please add a TODO item about it:
* Prevent long-lived temp tables from causing frozen-Xid advancement
starvation
>>
> Jeff Amiel wrote:
>> Can somebody explain this one to me? because of our auditing technique, we
>> have m
Jeff Amiel wrote:
>
> Bruce Momjian wrote:
>>>
>>> No, it isn't. Please add a TODO item about it:
>>> * Prevent long-lived temp tables from causing frozen-Xid advancement
>>>starvation
>
> Can somebody explain this one to me? because of our auditing technique, we
> have many LONG lived temp
Bruce Momjian wrote:
No, it isn't. Please add a TODO item about it:
* Prevent long-lived temp tables from causing frozen-Xid advancement
starvation
Can somebody explain this one to me? because of our auditing technique,
we have many LONG lived temp tables.(one per pooled
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> >
> > Is this item closed?
>
> No, it isn't. Please add a TODO item about it:
> * Prevent long-lived temp tables from causing frozen-Xid advancement
>starvation
Thanks. Added to TODO.
--
Bruce Momjian <[EMAIL PROTECTED]>http://mo
Andrew Hammond wrote:
> On 9/13/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> >
> > Alvaro Herrera wrote:
> > > Bruce Momjian wrote:
> > > >
> > > > Is this item closed?
> > >
> > > No, it isn't. Please add a TODO item about it:
> > > * Prevent long-lived temp tables from causing frozen-Xid adva
On 9/13/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> Alvaro Herrera wrote:
> > Bruce Momjian wrote:
> > >
> > > Is this item closed?
> >
> > No, it isn't. Please add a TODO item about it:
> > * Prevent long-lived temp tables from causing frozen-Xid advancement
> >starvation
>
> Sorry, I d
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> >
> > Is this item closed?
>
> No, it isn't. Please add a TODO item about it:
> * Prevent long-lived temp tables from causing frozen-Xid advancement
>starvation
Sorry, I don't understand this. Can you give me more text? Thanks.
--
Bruce
Bruce Momjian wrote:
>
> Is this item closed?
No, it isn't. Please add a TODO item about it:
* Prevent long-lived temp tables from causing frozen-Xid advancement
starvation
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prom
Is this item closed?
---
Alvaro Herrera wrote:
> Tom Lane wrote:
> > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > Tom Lane wrote:
> > >> Yeah, we had better investigate some way to clean them up. It was never
> > >> obv
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Oh, I was just thinking in way for Bruce to get out of his current
> situation.
Oh, for that a manual "drop table" as superuser should work fine.
regards, tom lane
---(end of broadcast)--
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Yeah, we had better investigate some way to clean them up. It was never
> >> obvious before that it mattered to get rid of orphan temp tables, but I
> >> guess it does.
>
> > Would it be enough to delete the tup
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Yeah, we had better investigate some way to clean them up. It was never
>> obvious before that it mattered to get rid of orphan temp tables, but I
>> guess it does.
> Would it be enough to delete the tuple from pg_class?
No, you nee
Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Well, it certainly seems like this shouldn't be happening. Maybe the
> > table belonged to a session that crashed, but the pg_class entry has not
> > been cleaned up -- possibly because that backend has not connected to
> > that part
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Well, it certainly seems like this shouldn't be happening. Maybe the
> table belonged to a session that crashed, but the pg_class entry has not
> been cleaned up -- possibly because that backend has not connected to
> that particular database.
Hm --- a
15 matches
Mail list logo