| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Barry Lind'" <barry(at)xythos(dot)com>, Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | RE: AW: Plans for solving the VACUUM problem |
| Date: | 2001-05-21 20:29:03 |
| Message-ID: | 3705826352029646A3E91C53F7189E3201663C@sectorbase2.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Correct me if I am wrong, but both cases do present a problem
> currently in 7.1. The WAL log will not remove any WAL files
> for transactions that are still open (even after a checkpoint
> occurs). Thus if you do a bulk insert of gigabyte size you will
> require a gigabyte sized WAL directory. Also if you have a simple
> OLTP transaction that the user started and walked away from for
> his one week vacation, then no WAL log files can be deleted until
> that user returns from his vacation and ends his transaction.
Todo:
1. Compact log files after checkpoint (save records of uncommitted
transactions and remove/archive others).
2. Abort long running transactions.
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2001-05-21 20:41:33 | Re: AW: Plans for solving the VACUUM problem |
| Previous Message | Tony Reina | 2001-05-21 20:28:20 | Re: Detecting readline in configure |