Thanks everyone. A more direct way to check via a sql function would be
better but I suppose the dblink extension method will work.
Thanks again,
Dennis
On Sat, Jul 6, 2024 at 9:38 AM Tom Lane wrote:
> Laurenz Albe writes:
> > On Fri, 2024-07-05 at 14:12 -0400, Dennis White wrote
Thanks for responding.
This will be a stored procedure written in plpgsql that's kicked off by
pg_cron.
I wasn't sure a normal smart shutdown would stop it.
Thanks
On Fri, Jul 5, 2024 at 4:57 PM Achilleas Mantzios <
a.mantz...@cloud.gatewaynet.com> wrote:
> Στις 5/7/24 21:1
My project's DB has a mutli-step stored procedure using Transaction Control
that may take 30 minutes or more to complete.
I am curious if there is a way to make it more smart shutdown friendly so
it can stop between steps?
We are using both PG 14 and PG 16 on Rhel 8.
Pardon me if it's obvious but
I'm surprised no one has mentioned perhaps it's a good idea to partition
this table while adding the pk. By your own statements the table is
difficult to work with as is. Without partitioning the table, row inserts
would need to walk the pk index and could be a factor. If this is static
table then
22 at 7:28 PM Tom Lane wrote:
> Dennis White writes:
> > Is there something I can do to allow users queries to use the index with
> a
> > condition like that used for the table owner's query?
>
> It looks like the problem in your badly-optimized query is that
> ther
My project is using PostgreSQL 12.9 and has a table that gets millions of
positions of ships every day. It is partitioned by tier (the importance of
position) and sub-partitioned by time.
We also use RLS to restrict access to rows in the table.
Our problem is the query planner will not let user qu
