On Fri, Jan 14, 2022 at 11:31 AM Stephen Frost wrote:
> Greetings,
>
> * Issa Gorissen (issa-goris...@usa.net) wrote:
> > Thx a lot. I thought about it but was not so sure about having a complex
> > script (compared to the very simple version when using the exclusive
> backup
> > - but this this
On Sat, Jan 15, 2022 at 5:23 PM Mladen Gogala
wrote:
> On 1/14/22 16:00, David G. Johnston wrote:
>
> I still don't really understand what is so great about it. About its only
> redeeming feature is a declaration that "it is in core" and that newcomers
> can just default to it without thinking.
Mladen Gogala writes:
> On 1/13/22 18:35, Tom Lane wrote:
>> .. or else reduce the number of partitions you're using. (People
>> frequently seem to think that more partitions are free. That is
>> extremely not true. I generally think that if you're using more
>> than a few dozen partitions per
On 1/15/22 16:23, Mladen Gogala wrote:
On 1/14/22 16:00, David G. Johnston wrote:
I still don't really understand what is so great about it. About its
only redeeming feature is a declaration that "it is in core" and that
newcomers can just default to it without thinking. I'd rather just
play
On 1/14/22 16:00, David G. Johnston wrote:
I still don't really understand what is so great about it. About its
only redeeming feature is a declaration that "it is in core" and that
newcomers can just default to it without thinking. I'd rather just
play favorites and write "use pgbackrest" in
On 1/13/22 18:35, Tom Lane wrote:
.. or else reduce the number of partitions you're using. (People
frequently seem to think that more partitions are free. That is
extremely not true. I generally think that if you're using more
than a few dozen partitions per table, you are making a mistake.)
On 1/14/22 3:42 PM, Adrian Klaver wrote:
On 1/14/22 13:04, Daniel Westermann (DWE) wrote:
On 1/14/22 1:40 PM, Stephen Frost wrote:
snip]
We shouldn't be trying to provide
documentation around how to write a tool like pgbackrest, we should,
instead, have a tool like pgbackrest in core with its o
The goal was to limit access to the schema to users who manage roles, in
all likelihood to a specific group of administrators. This can be done with
this solution. I have no problem with managing roles through plpgsql
functions. There has been no need to create databases until now. In my
solution,
