Re: pgbackrest info of encrypted seems broken
От | David Steele |
---|---|
Тема | Re: pgbackrest info of encrypted seems broken |
Дата | |
Msg-id | 9d922ff3-93d5-bcbe-b02a-22a4bd6e80f1@pgmasters.net обсуждение исходный текст |
Ответ на | Re: pgbackrest info of encrypted seems broken (Ron <ronljohnsonjr@gmail.com>) |
Список | pgsql-general |
On 5/19/21 1:42 PM, Ron wrote: > On 5/19/21 12:08 PM, David Steele wrote: >> On 5/19/21 9:47 AM, Ron wrote: >>> >>> This is on Postgresql 9.6, if it matters. Attached is a text file >>> showing the pgbackrest version, config, backup log and "pgbackrest >>> info" output. >>> >>> I followed the instructions in >>> https://pgbackrest.org/user-guide.html#quickstart/configure-encryption, >>> and successfully ran these commands before the first encrypted >>> backup, but they aren't in the text file: >>> rm -r /Database/9.6/backups/pgbackrest >>> pgbackrest stanza-create --stanza=localhost >>> >>> Have I misconfigured something? >> >> If the cipher is configured per stanza then the info command must be >> run per stanza, e.g. >> >> pgbackrest --stanza=localhost info >> >> If the cipher settings were in [global] this would work as expected, >> but of course there may be valid reasons to set the cipher at the >> stanza level. Essentially, if you run the info command without >> --stanza it has no knowledge of stanza-level settings. > > Both of those solved the problem. I wound up moving it up to [global]. > >> >> We've known about this internally for a while, but have never seen it >> expressed in the field. If this is a blocker for you (i.e. you can't >> put the cipher settings in [global]) then feel free to open a Gtihub >> issue (https://github.com/pgbackrest/pgbackrest/issues) so it is on >> our radar. > > What I suggest is documenting this. :) Issue #1407. Documenting it sounds like a good plan. Regards, -- -David david@pgmasters.net
В списке pgsql-general по дате отправления: