Re: Database logins taking longer and longer, showing up as "authentication" in ps(1)

2020-09-30 Thread Adam Sjøgren
Best regards, Adam -- "Don't think twice Adam Sjøgren It's all right" a...@koldfront.dk

Re: Database logins taking longer and longer, showing up as "authentication" in ps(1)

2020-09-30 Thread Adam Sjøgren
worker > entry/exit might be contributing to the overall load on ProcArrayLock. Best regards, Adam -- "That's one of the remarkable things about life. Adam Sjøgren It's never so bad that it can't get worse." a...@koldfront.dk

Re: Database logins taking longer and longer, showing up as "authentication" in ps(1)

2020-08-20 Thread Adam Sjøgren
actions per second plotted: · https://koldfront.dk/misc/postgresql/postgres_transactions_ALL-pinpoint_1597799383-1597907383.png (I think the hole in the graph is when Munin timed out getting the information, and the number of transactions dropped as I stopped most of the workers.) Best regards, Adam -- "Examination and mastering of a new highly Adam Sjøgren intellectual equipment was a hard labour." a...@koldfront.dk

Re: Database logins taking longer and longer, showing up as "authentication" in ps(1)

2020-08-19 Thread Adam Sjøgren
e know if there are any parameters I should try adjusting, or some other information I should try to extract. Thanks! Best regards, Adam -- "Why do you ask so much?" Adam Sjøgren "I'm a kid. It's what we do." a...@koldfront.dk

Re: Database logins taking longer and longer, showing up as "authentication" in ps(1)

2020-08-19 Thread Adam Sjøgren
Tom writes: > Stephen Frost writes: >> * Adam Sjøgren (a...@koldfront.dk) wrote: >>> Sometimes new database logins slow down, from usually taking <0.05s to >>> taking minutes. This is for psql as a normal user using Kerberos, for >>> psql as the post

Re: Database logins taking longer and longer, showing up as "authentication" in ps(1)

2020-08-18 Thread Adam Sjøgren
Stephen writes: > * Adam Sjøgren (a...@koldfront.dk) wrote: >> >> We have 60 processes (workers) running on different machines accessing >> the database, that all grab jobs from a queue and update rows in a table >> after doing some calculations (which vary

Re: Database logins taking longer and longer, showing up as "authentication" in ps(1)

2020-08-18 Thread Adam Sjøgren
Laurenz writes: > On Tue, 2020-08-18 at 14:53 +0200, Adam Sjøgren wrote: >> >> We have 60 processes (workers) running on different machines accessing >> the database, that all grab jobs from a queue and update rows in a table >> after doing some calculations (

Database logins taking longer and longer, showing up as "authentication" in ps(1)

2020-08-18 Thread Adam Sjøgren
l.org/message-id/CAJw8uJQGoobesbPCMbxj6Vb4nv9D-GgvZ%2B7pK%2Bfckbb4DqJEAg%40mail.gmail.com and https://www.postgresql.org/message-id/20140312232810.634.7997%40wrigleys.postgresql.org -- "We don't care about crashing our cars Adam Sjøgren Pedal to the metal and our heads among the stars"a...@koldfront.dk

Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100

2018-04-10 Thread Adam Sjøgren
r toast value 16396 in pg_toast_16384 Best regards, Adam -- "No more than that, but very powerful all theAdam Sjøgren same; simple things are good."a...@novozymes.com

Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100

2018-04-05 Thread Adam Sjøgren
when the server does ...] Best regards, Adam -- "No more than that, but very powerful all theAdam Sjøgren same; simple things are good."a...@novozymes.com

Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100

2018-04-05 Thread Adam Sjøgren
98750544 | 1 | (39575142,4) | 1510704835 |0 |716 (2 rows) Let me know what other relevant info I can provide. Best regards, Adam -- "No more than that, but very powerful all theAdam Sjøgren same; simple things are good."a...@novozymes.com

Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100

2018-01-16 Thread Adam Sjøgren
Michael writes: > On Tue, Jan 16, 2018 at 07:05:19PM +0100, Adam Sjøgren wrote: >> This sounds very interesting - we are running PostgreSQL 9.3.20. > Which means that we may be looking at a new bug, 9.3.20 is the latest in > the 9.3 set as of today. Yes; unfortunately

Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100

2018-01-16 Thread Adam Sjøgren
ers for a > while . > > Is this running on postgresql 9.4.8? Because mine was fixed upgrading to > 9.4.11 , a bug indeed . > > > > Kind regards > > > > Jorge Daniel Fernandez > > > ____ > From: Adam Sjøgren <a...@no