On 10/18/23 03:07, Peter Eisentraut wrote:
On 16.10.23 17:15, David Steele wrote:
I also do wonder with recovery_control is really a better name. Maybe
I just have backup_label too firmly stuck in my head, but is what that
file does really best described as recovery control? I'm not so sure
abou
On 16.10.23 17:15, David Steele wrote:
I also do wonder with recovery_control is really a better name. Maybe
I just have backup_label too firmly stuck in my head, but is what that
file does really best described as recovery control? I'm not so sure
about that.
The thing it does that describes i
On Mon, 2023-10-16 at 12:12 -0400, Robert Haas wrote:
> On Mon, Oct 16, 2023 at 12:06 PM Michael Banck wrote:
> > Not sure what to do about this, but as people/companies start moving to
> > 15, I am afraid we will get people complaining about this. I think
> > having exclusive mode still be the de
On 10/16/23 12:12, Robert Haas wrote:
On Mon, Oct 16, 2023 at 12:06 PM Michael Banck wrote:
Not sure what to do about this, but as people/companies start moving to
15, I am afraid we will get people complaining about this. I think
having exclusive mode still be the default for pg_start_backup()
On 10/16/23 12:06, Michael Banck wrote:
On Mon, Oct 16, 2023 at 11:15:53AM -0400, David Steele wrote:
On 10/16/23 10:19, Robert Haas wrote:
We got rid of exclusive backup mode. We replaced pg_start_backup
with pg_backup_start.
I do think this was an improvement. For example it allows us to
On Mon, Oct 16, 2023 at 12:06 PM Michael Banck wrote:
> Not sure what to do about this, but as people/companies start moving to
> 15, I am afraid we will get people complaining about this. I think
> having exclusive mode still be the default for pg_start_backup() (albeit
> deprecated) in one relea
On Mon, Oct 16, 2023 at 11:15:53AM -0400, David Steele wrote:
> On 10/16/23 10:19, Robert Haas wrote:
> > We got rid of exclusive backup mode. We replaced pg_start_backup
> > with pg_backup_start.
>
> I do think this was an improvement. For example it allows us to do
> [1], which I believe is a be
On 10/16/23 10:19, Robert Haas wrote:
On Sat, Oct 14, 2023 at 2:22 PM David Steele wrote:
I was recently discussing the complexities of dealing with pg_control
and backup_label with some hackers at PGConf NYC, when David Christensen
commented that backup_label was not a very good name since it
On Sat, Oct 14, 2023 at 2:22 PM David Steele wrote:
> I was recently discussing the complexities of dealing with pg_control
> and backup_label with some hackers at PGConf NYC, when David Christensen
> commented that backup_label was not a very good name since it gives the
> impression of being inf
On 10/16/23 00:26, Kyotaro Horiguchi wrote:
At Mon, 16 Oct 2023 13:16:42 +0900 (JST), Kyotaro Horiguchi
wrote in
Just an idea in a slightly different direction, but I'm wondering if
we can simply merge the content of backup_label into control file.
The file is 8192 bytes long, yet only 256 byt
On Mon, Oct 16, 2023 at 01:16:42PM +0900, Kyotaro Horiguchi wrote:
> Just an idea in a slightly different direction, but I'm wondering if
> we can simply merge the content of backup_label into control file.
> The file is 8192 bytes long, yet only 256 bytes are used. As a result,
> we anticipate no
At Mon, 16 Oct 2023 13:16:42 +0900 (JST), Kyotaro Horiguchi
wrote in
> Just an idea in a slightly different direction, but I'm wondering if
> we can simply merge the content of backup_label into control file.
> The file is 8192 bytes long, yet only 256 bytes are used. As a result,
> we anticipat
l people seemed to think it was a good idea.
>
> Attached is a patch to rename backup_label to recovery_control. The
Just an idea in a slightly different direction, but I'm wondering if
we can simply merge the content of backup_label into control file.
The file is 8192 bytes long, yet o
backup_label to recovery_control. The
purpose is to make it more obvious that the file should not be deleted.
I'm open to other names, e.g. recovery.control. That makes the naming
distinct from tablespace_map, which is perhaps a good thing, but is also
more likely to be confused with recovery.s
14 matches
Mail list logo
