Re: Data loss, vacuum, transaction wrap-around

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql(at)mohawksoft(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Data loss, vacuum, transaction wrap-around
Date: 2005-02-18 18:19:19
Message-ID: 421631A7.9010706@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> pgsql(at)mohawksoft(dot)com writes:
>
>>In fact, I think it is so bad, that I think we need to back-port a fix to
>>previous versions and issue a notice of some kind.
>
>
> They already do issue notices --- see VACUUM.
>
> A real fix (eg the forcible stop we were talking about earlier) will not
> be reasonable to back-port.

Would at least a automated warning mechanism be a reasonable backport?

Sincerely,

Joshua D. Drake

>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faq

--
Command Prompt, Inc., your source for PostgreSQL replication,
professional support, programming, managed services, shared
and dedicated hosting. Home of the Open Source Projects plPHP,
plPerlNG, pgManage, and pgPHPtoolkit.
Contact us now at: +1-503-667-4564 - http://www.commandprompt.com

Attachment Content-Type Size
jd.vcf text/x-vcard 640 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-02-18 18:37:14 Re: Data loss, vacuum, transaction wrap-around
Previous Message Tom Lane 2005-02-18 18:03:26 Re: Data loss, vacuum, transaction wrap-around