From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | paul(dot)hatcher(at)sentinelpartners(dot)co(dot)uk |
Subject: | BUG #16540: Possible corrupted file? |
Date: | 2020-07-14 08:10:23 |
Message-ID: | 16540-260c70662eaf5851@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 16540
Logged by: Paul Hatcher
Email address: paul(dot)hatcher(at)sentinelpartners(dot)co(dot)uk
PostgreSQL version: 11.8
Operating system: Windows Server 2012
Description:
We had a situation where a query that normally ran in 10 seconds instead
never completed. No conflicts or locks could be seen. All indexes were
valid and in place. A full shutdown and restart of the server was done with
no effect.
To test we took a full backup of this system and restored to an identical
alternate system. Having done this, the alternate system ran the query in
10 seconds.
Final test was to backup and restore back into the production system -
having done this the query returned to running in 10 seconds. Do you have
any idea what could have caused this?
Thanks
Paul
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Ellis | 2020-07-14 09:00:18 | Re: Small query using LATERAL that segfaults Postgres |
Previous Message | David G. Johnston | 2020-07-14 06:06:06 | Re: BUG #16539: About pg_logdir_ls() function and pg_ls_logdir()function |