Hi Stephen,
Thanks for your response.
> Not sure what 'traditional zip method' means here, but if you've copied
the shell script out of the documentation, that's not a safe
configuration.
Conventional zip method means my archive_command and restore_command parameters
are as follows,
archive_co
On Tue, Sep 27, 2022 at 08:47:52PM -0700, Bryn Llewellyn wrote:
>
> For example, the "lower case only" rule was meant to be an
> example of *any* data rule. Just like the write-once-read-many auto-generated
> surrogate primary key rule. Can you show me how those data rules, unrealistic
> as you mig
Bryn Llewellyn writes:
> rjuju...@gmail.com wrote:
>> I'm not convinced... that the authorization system can prevent an untrusted
>> user with a direct SQL access from actually hurting you.
> What do you mean by "untrusted"? Any person who is given the credentials
> to start a database session i
> rjuju...@gmail.com wrote:
>
> b...@yugabyte.com wrote:
>>
>> Now back to my new thread. I interpreted what Tom wrote to mean that he
>> flatly rejected the idea that a database design was possible that prevented
>> a client session that authorized as a role, that's designed for that
>> purpo
On Tue, Sep 27, 2022 at 07:29:39PM -0700, Bryn Llewellyn wrote:
>
> Now back to my new thread. I interpreted what Tom wrote to mean that he
> flatly rejected the idea that a database design was possible that prevented a
> client session that authorized as a role, that's designed for that purpose,
>
> rjuju...@gmail.com wrote:
>
>> b...@yugabyte.com wrote:
>>
hjp-pg...@hjp.at wrote:
> rjuju...@gmail.com wrote:
>
>> b...@yugabyte.com wrote:
>>
>> [Bryn] My demo seems to show that when a program connects as "client",
>> it can perform exactly and only the
On Tue, Sep 27, 2022 at 05:27:22PM -0700, Bryn Llewellyn wrote:
> > hjp-pg...@hjp.at wrote:
> >
> >> rjuju...@gmail.com wrote:
> >>
> >>> b...@yugabyte.com wrote:
> >>>
> >>> My demo seems to show that when a program connects as "client", it can
> >>> perform exactly and only the database operation
> hjp-pg...@hjp.at wrote:
>
>> rjuju...@gmail.com wrote:
>>
>>> b...@yugabyte.com wrote:
>>>
>>> My demo seems to show that when a program connects as "client", it can
>>> perform exactly and only the database operations that the database design
>>> specified. Am I missing something? In other
> rjuju...@gmail.com wrote:
>
>> b...@yugabyte.com wrote:
>>
>> My demo seems to show that when a program connects as "client", it can
>> perform exactly and only the database operations that the database design
>> specified. Am I missing something? In other words, can anybody show me a
>> vul
On 2022-09-27 14:58:58 +0800, Julien Rouhaud wrote:
> On Mon, Sep 26, 2022 at 11:18:34AM -0700, Bryn Llewellyn wrote:
> > My demo seems to show that when a program connects as "client", it can
> > perform exactly and only the database operations that the database design
> > specified.
> >
> > Am I
I've changed the code to use order by in the aggregate and it seems
there are no noticeable changes in the query performance.
Thanks for the help.
Best,
Federico Caselli
On Sun, 25 Sept 2022 at 00:30, Federico wrote:
>
> Understood, thanks for the explanation.
> I'll work on updating the queries
Hi Andreas,
no really what you are looking for, i know, but we have
pg_stat_user_tables. There can you find how often the table was queried
in the past. Take the data, wait some time, take it again and compare.
Thanks for this idea. i will try it out.
Andreas
On Tue, 2022-09-27 at 08:35 +0200, Andreas Kretschmer wrote:
>
>
> Am 26.09.22 um 14:05 schrieb Andreas Fröde:
> > Hello,
> > I am looking for a way to find out when a table was last used for
> > reading. (Without writing every statement in the logfile or putting a
> > trigger on it). Is there
Greetings,
* Inzamam Shafiq (inzamam.sha...@hotmail.com) wrote:
> I am in process of configuring pgbackrest, I have followed documents and
> configured backup from backup server. I have a setup of Primary and Hot
> Standby, when I configured pgbackrest the standby DB got un-synced and now I
> a
14 matches
Mail list logo
