From: | Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> |
Subject: | Re: CREATE DATABASE with filesystem cloning |
Date: | 2024-05-21 08:18:34 |
Message-ID: | CAN55FZ08c9kJO_5t3jJn0PvLuV44=1t_Pm_7UjLb3SqPkKkQtw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Thu, 16 May 2024 at 17:47, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Thu, May 16, 2024 at 9:43 AM Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:
> > Actually, the documentation for the file_copy_method was mentioning
> > the things it controls; I converted it to an itemized list now. Also,
> > changed the comment to: 'Further uses of this function requires
> > updates to the list that GUC controls in its documentation.'. v7 is
> > attached.
>
> I think the comments need some wordsmithing.
I changed it to 'Uses of this function must be documented in the list
of places affected by this GUC.', I am open to any suggestions.
> I don't see why this parameter should be PGC_POSTMASTER.
I changed it to 'PGC_USERSET' now. My initial point was the database
or tablespace to be copied with the same method. I thought copying
some portion of the database with the copy and rest with the clone
could cause potential problems. After a bit of searching, I could not
find any problems related to that.
v8 is attached.
--
Regards,
Nazir Bilal Yavuz
Microsoft
Attachment | Content-Type | Size |
---|---|---|
v8-0001-Introduce-file_copy_method-GUC.patch | text/x-patch | 12.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrei Lepikhov | 2024-05-21 09:01:19 | Re: POC: GROUP BY optimization |
Previous Message | Bertrand Drouvot | 2024-05-21 07:22:57 | Re: Avoid orphaned objects dependencies, take 3 |