There is no reason to use index. The query has neither WHERE nor ORDER BY
clause.
Toomas
> On 23. Oct 2023, at 18:13, Олег Самойлов wrote:
>
> Back pardon, but I have a very newbie question. I have a partitioned table,
> partitioned by primary bigint key, size of partition 1000
user;
SET
6) db=> select current_user, session_user;
current_user | session_user
--+--
db_user | db_user
(1 row)
7) db=> \password
Enter new password:
Enter it again:
db=>
I hope this explains.
BR,
Toomas
> On 21. Oct 2021, at 19:13, Adrian Klaver wrote
setup where session_user is changed automatically as
database owner when user logs into database.
BR,
Toomas
> On 20. Oct 2021, at 18:43, Vijaykumar Jain
> wrote:
>
>
>
> On Wed, 20 Oct 2021 at 20:52, Adrian Klaver <mailto:adrian.kla...@aklaver.com>> wrote:
> O
Hi Adrian,
Thank you for your help. The issue was that when user logged into database his
session_user user was set as owner of database automatically. User had success
to change password when session_user = current_user was set before.
BR,
Toomas
> On 20. Oct 2021, at 17:45, Adrian Kla
BR,
Toomas
And please be sure that default permissions are defined properly. Otherwise it
may happen that userA creates a new table but userB has access for that.
Alternative option is that user has to grant proper access for the role group
after every time when a new db object is created.
Toomas
>
from standby
node as soon as possible in order to release all possible locks/blockers on
master that may cause bloating.
BR,
Toomas
> On 24. Jun 2020, at 11:31, RAJAMOHAN wrote:
>
> Hello all,
>
> Your expertise is needed on this. I was going through previous mails
> regard
is active on standby host.
BR,
Toomas
q_recvbuf, pqcomm.c:978
Does it give any hints for anyone? Or how to find right version of source code
what to analyse?
BR,
Toomas
but doesn’t help me about suspended replication. All
worked with same configuration on Postgres version 10.6, the issue started
after version upgrade.
This is the reason why I am very keen to find out real cause for the conflict.
BR,
Toomas
identify where is the conflict that stops replication and forces to
terminate a query on standby host?
BR,
Toomas
> On 17. Jun 2020, at 16:38, Toomas Kristin wrote:
>
> Hi Laurenz,
>
> Thank you!
>
> What are reasons for conflicts? Based on documentation seems that the
. isnt it? Or there can be some other
reasons?
I just wondering what would be impact when I increase value for
autovacuum_vacuum_scale_factor in order force vacuuming process postpone the
clean up process.
BR,
Toomas
> On 17. Jun 2020, at 12:42, Laurenz Albe wrote:
>
> On Wed, 2020
vacuuming process on master.
Is there any changes on version 11.5 what may cause it?
Is there any good solution without setting max_standby_streaming_delay=-1 or
enabling hot_standby_feedback?
BR,
Toomas
experience?
Toomas
14 matches
Mail list logo
