Hello! I'm having trouble with LISTEN/NOTIFY speed. Now I have about
100-200 (few?) clients who are actively messaging. But recently I started to
notice a drop in speed. Changing the log_min_duration_statement parameter did
not show slow queries in the log.
As it turned out, the pg_noti
Hello,
We tried importing into an empty database in PG 12 from the dump that was
created in PG 10. Import was successful but we got an message that an error was
ignored. We agin imported with -e option and the following message was printed:
pg_restore: while PROCESSING TOC:
pg_restore: from TO
On 3/14/22 06:39, Shukla, Pranjal wrote:
Hello,
We tried importing into an empty database in PG 12 from the dump that
was created in PG 10. Import was successful but we got an message that
an error was ignored. We agin imported with -e option and the following
message was printed:
pg_restor
=?UTF-8?B?0JDRgNGB0LXQvSDQkNGA0YPRgtGO0L3Rj9C9?= writes:
> Hello! I'm having trouble with LISTEN/NOTIFY speed. Now I have about
> 100-200 (few?) clients who are actively messaging. But recently I started to
> notice a drop in speed. Changing the log_min_duration_statement parameter did
> no
For the update processes, all other tables are read-only reference tables,
I don't think they would be locked.
iGLASS Networks
www.iglass.net
On Fri, Mar 11, 2022 at 10:03 PM Michael Lewis wrote:
> Could you set lock_timeout, lock table explicitly for SHARE UPDATE
> EXCLUSIVE (pretty sure tha
How many partitions do you expect to have? Why are you partitioning on that
column? Do you have need to drop old data all at the same time? How many
rows in each partition or in total do you expect to have?
