| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Index recreation in vacuum |
| Date: | 2000-01-19 03:22:00 |
| Message-ID: | 200001190322.WAA14508@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> In addition,rename(),unlink(),mv aren't preferable for transaction
> control as far as I see. We couldn't avoid inconsistency using
> those OS functions.
> We have to wait the change of relation file naming if copying
> vacuum is needed.
> Under the spec we need not rename(),mv etc.
Are you worried the system may crash in the middle of renaming one
table, but not the indexes. That would be a serious problem.
I see now. I can't think of a way around that. The rename() itself is
atomic.
--
Bruce Momjian | http://www.op.net/~candle
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 | Thomas Lockhart | 2000-01-19 03:30:43 | Re: Date/time types (Re: [HACKERS] Re: [COMMITTERS] pgsql/src/include/catalog(pg_type.h)) |
| Previous Message | Hiroshi Inoue | 2000-01-19 03:10:32 | RE: [HACKERS] Index recreation in vacuum |