Hi Steve,
I happened to see the pg_cron extensions these days, IMHO this is
not a bug, pg_cron has two kind of bg workers, one is the launcher
and the other is CronBackgroundWorker, the launcher is responsible
for scheduling the jobs, and CronBackgroundWorker is the real worker
doing the job.
See
"Dirschel, Steve" writes:
> I believe this clearly points to an issue with pg_cron. Would you agree?
Yeah, you certainly need to look into what sort of environment
that is setting up. I know zip about pg_cron, can't help you
there.
regards, tom lane
> "Dirschel, Steve" writes:
>> setdatabase | setrole |
>>
>> setconfig
>> -+-+--
>> -
"Dirschel, Steve" writes:
> setdatabase | setrole |
>
> setconfig
> -+-+-
We recently upgraded from postgres 12.8 to 14.3. We are running
Aurora Postgres on AWS.
>Aurora Postgres != Postgres. This doesn't seem like something they'd change,
>but we can't rule that out entirely.
>>> Try:
>>> select setting, source, sourcefile, pending_restart from pg_settin
"Dirschel, Steve" writes:
>>> We recently upgraded from postgres 12.8 to 14.3. We are running
>>> Aurora Postgres on AWS.
Aurora Postgres != Postgres. This doesn't seem like something they'd
change, but we can't rule that out entirely.
>> Try:
>> select setting, source, sourcefile, pending_re
>On 9/6/22 12:07, Dirschel, Steve wrote:
>> We recently upgraded from postgres 12.8 to 14.3. We are running
>> Aurora Postgres on AWS.
>>
>> We have procedures that will make calls to RAISE NOTICE to write out
>> messages if you interactively call the procedure through psql. These
>> procedur
On 9/6/22 12:07, Dirschel, Steve wrote:
We recently upgraded from postgres 12.8 to 14.3. We are running Aurora
Postgres on AWS.
We have procedures that will make calls to RAISE NOTICE to write out
messages if you interactively call the procedure through psql. These
procedures are getting ca
We recently upgraded from postgres 12.8 to 14.3. We are running Aurora
Postgres on AWS.
We have procedures that will make calls to RAISE NOTICE to write out messages
if you interactively call the procedure through psql. These procedures are
getting called by pg_cron.
Since upgrading these RA
