| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Christoph Berg <myon(at)debian(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: fsync-pgdata-on-recovery tries to write to more files than previously |
| Date: | 2015-05-26 17:13:40 |
| Message-ID: | 20150526171340.GC5310@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-05-26 19:07:20 +0200, Andres Freund wrote:
> Abhijit, do you recall why the code was changed to follow all symlinks
> in contrast to explicitly going through the tablespaces as initdb -S
> does? I'm pretty sure early versions of the patch pretty much had a
> verbatim copy of the initdb logic?
Forgot to add Abhijit to CC list, sorry.
> That [initdb's] logic is missing pg_xlog btw, which is bad for pg_upgrade.
On second thought it's probably not actually bad for pg_upgrade's
specific usecase. It'll always end with a proper shutdown, so it'll
never need that WAL. But it'd be bad if anybody ever relied on initdb -S
in a different scenario.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christoph Berg | 2015-05-26 17:27:14 | Re: Why does txid_current() assign new transaction-id? |
| Previous Message | Andres Freund | 2015-05-26 17:07:20 | Re: fsync-pgdata-on-recovery tries to write to more files than previously |