| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: file cloning in pg_upgrade and CREATE DATABASE |
| Date: | 2018-02-22 22:49:48 |
| Message-ID: | 9a3df7ee-6bc1-2ba6-7253-134e5bb9a943@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2/21/18 18:57, Tomas Vondra wrote:
> Nice improvement, of course. How does that affect performance on the
> cloned database? If I understand this correctly, it essentially enables
> CoW on the files, so what's the overhead on that? It'd be unfortunate to
> speed up CREATE DATABASE only to get degraded performance later.
I ran a little test (on APFS and XFS): Create a large (unlogged) table,
copy the database, then delete everything from the table in the copy.
That should need to CoW all the blocks. It has about the same
performance with cloning, possibly slightly faster.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2018-02-22 22:54:33 | Re: Translations contributions urgently needed |
| Previous Message | Peter Geoghegan | 2018-02-22 21:29:12 | Re: Hash Joins vs. Bloom Filters / take 2 |