Re: Vacuum/visibility is busted

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Vacuum/visibility is busted
Date: 2013-06-19 22:01:44
Message-ID: CAMkU=1xoCH4qP0F2Mgg0uvPev4ZQif7B+rRXouwKqNV2w2TZOg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 7, 2013 at 12:01 PM, Andres Freund <andres(at)2ndquadrant(dot)com>wrote:

> On 2013-02-07 11:15:46 -0800, Jeff Janes wrote:
> >
> > Does anyone have suggestions on how to hack the system to make it
> > fast-forward the current transaction id? It would certainly make
> > testing this kind of thing faster if I could make transaction id
> > increment by 100 each time a new one is generated. Then wrap-around
> > could be approached in minutes rather than hours.
>
> I had various plpgsql functions to do that, but those still took quite
> some time. As I needed it before I just spent some minutes hacking up a
> contrib module to do the job.
>

Hi Andres,

Your patch needs the file "xidfuncs--1.0.sql", but does not include it.

I could probably guess what needs to be in that file, but do you still have
a copy of it?

>
> I doubt it really think it makes sense as a contrib module on its own
> though?
>

Maybe PGXN?

Cheers,

Jeff

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Claudio Freire 2013-06-19 22:02:28 Re: Implementing incremental backup
Previous Message Jeff Janes 2013-06-19 21:50:07 Re: Git-master regression failure