| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
| Cc: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: After ~Crash Sequence not correct |
| Date: | 2002-01-03 05:57:13 |
| Message-ID: | 200201030557.g035vDA14407@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Mikheev, Vadim wrote:
> > I have verified that killing the postmaster after a few nextval's
> > leaves things in a bad state after restart.
> >
> > I think I see the problem: in nextval(), the sequence data written to
> > the WAL log is different from that written to the data page. Isn't
> > that bogus?
>
> It was made to avoid WAL-loging on each nextval call, ie it should work
> like OID pre-fetching: value stored in WAL must always "exceed" values
> returned by nextval so on the after-crash-restart sequence should be
> advanced to value which was never returned by nextval (for non-cycled
> sequences). Maybe I made some mistakes in implementation?
Was this ever fixed?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-01-03 08:13:38 | Re: Bug #548: Misleading documentation of `palloc' |
| Previous Message | Dmitry Fomichev | 2002-01-03 01:29:03 | Refcursor problem |