From: | Dennis White <dwhite(at)seawardmoon(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Can a long running procedure detect when smart shutdown is pending? |
Date: | 2024-07-06 17:17:08 |
Message-ID: | CAE=rie9qABQffaU+ZQ2FnDtK3Sf9KaG4uruzFYR3AWCqJ=Va5g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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 <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> writes:
> > On Fri, 2024-07-05 at 14:12 -0400, Dennis White wrote:
> >> 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?
>
> > I don't think there is a direct way to do that in SQL; that would
> require a new
> > system function that exposes canAcceptConnections() in SQL.
>
> It's worse than that: the state variables involved are local to the
> postmaster, so you wouldn't get the right answer in a backend even
> if the function were reachable.
>
> > What you could do is use the dblink extension to connect to the local
> database.
> > If you get an error "the database system is shutting down", there is a
> smart
> > shutdown in progress.
>
> This'd probably work. Ugly, but ...
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | sud | 2024-07-06 20:02:33 | Re: Load a csv or a avro? |
Previous Message | Michael Nolan | 2024-07-06 13:50:42 | Re: Alignment check |