| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Denis Perchine'" <dyp(at)perchine(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | RE: (one more time) Patches with vacuum fixes available . |
| Date: | 2001-01-25 00:55:13 |
| Message-ID: | 8F4C99C66D04D4118F580090272A7A234D32BA@sectorbase1.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Did we decide against LAZY? Seems we have a number of people
> concerned about vacuum downtime, and I can see this as a win
> for them. If they don't specify LAZY, the code is not run.
First sorry that I wasn't able to deal with vlazy earlier.
Now I have one more open item for 7.1 - restoring index structure
at runtime (add tuple to parent page for aborted split op,
create root page if no one exists). I'll try to deal with both
items (in any case vlazy will be ported to 7.1, as required
by contract).
As for reported problem: I just looked at Denis' tgz and
found only table, index and sequence(?) data files - I would
need in schema definitions, pg_log and pg_variable files
as well. Denis? Also, when these copies were made -
before/after unsuccessful vacuum+lazy?
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2001-01-25 01:22:42 | Bad REFERENCES behaviour |
| Previous Message | Bruce Momjian | 2001-01-25 00:05:13 | Re: Re: postgresql.conf and postgres options |