From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Adam Sjøgren <asjo(at)koldfront(dot)dk> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org, Stephen Frost <sfrost(at)snowman(dot)net> |
Subject: | Re: Database logins taking longer and longer, showing up as "authentication" in ps(1) |
Date: | 2020-09-30 21:41:22 |
Message-ID: | 734ad6fb-3cf1-d4c5-6158-cb00de7813fa@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 9/30/20 2:30 PM, Adam Sjøgren wrote:
> Adrian writes:
>
>> I don't have an answer. Not even sure if this is relevant to the
>> problem, but how are the jobs getting into the queue?
>
> Plain INSERTs - often a lot at the same time. I inserted 400K jobs to
> clean up after a bug earlier today, for instance.
>
> What were you suspecting?
Honestly a fishing expedition. All the discussion, as far as I could
remember, had to do with the retrieval part of the process. Just thought
for completeness it might be useful to flesh out the insertion portion
of the process. Though it does get one to wondering how the appearance
of a large number of jobs at once affects the those programs looking for
new jobs?
>
>
> Best regards,
>
> Adam
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Lewis | 2020-09-30 22:15:46 | Re: Database logins taking longer and longer, showing up as "authentication" in ps(1) |
Previous Message | Adam Sjøgren | 2020-09-30 21:30:04 | Re: Database logins taking longer and longer, showing up as "authentication" in ps(1) |