| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>, pgsql-bugs(at)postgreSQL(dot)org |
| Subject: | Re: After ~Crash Sequence not correct |
| Date: | 2001-12-19 18:36:46 |
| Message-ID: | 3705826352029646A3E91C53F7189E32518454@sectorbase2.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> 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?
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bill Studenmund | 2001-12-19 18:40:44 | Re: Unable to compare _bpchar for similarity in WHERE-clause |
| Previous Message | Tom Lane | 2001-12-19 17:39:18 | Re: After ~Crash Sequence not correct |