| From: | Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: initdb -S and tablespaces |
| Date: | 2014-09-29 10:13:32 |
| Message-ID: | 20140929101332.GA32005@toroid.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 2014-09-29 11:54:10 +0200, andres(at)2ndquadrant(dot)com wrote:
>
> Note that the perform_fsync() *was* ok for its original purpose in
> initdb. At the end of initdb there's no relevant tablespaces. But if
> used *after* pg_upgrade, that's not necessarily the case.
Right.
So, since I'm writing a function to fsync everything inside PGDATA
anyway, it makes sense to call it both from initdb and StartupXLOG.
It'll do what initdb -S now does, plus follow links in pg_tblspc.
Any suggestions about where to put such a function? (I was looking at
backend/utils/init, but I'm not sure that's a good place for this.)
-- Abhijit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | furuyao | 2014-09-29 10:13:59 | Re: pg_receivexlog --status-interval add fsync feedback |
| Previous Message | Andres Freund | 2014-09-29 09:54:10 | Re: initdb -S and tablespaces |