Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault

2022-11-07 Thread Stefan Froehlich
On Mon, Nov 07, 2022 at 09:02:26AM -0500, Tom Lane wrote: > Stefan Froehlich writes: > > On Mon, Nov 07, 2022 at 08:17:10AM -0500, Mladen Gogala wrote: > >> On 11/7/22 06:19, Laurenz Albe wrote: > >>> Don't continue to work with that cluster even if everything s

Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault

2022-11-07 Thread Stefan Froehlich
On Mon, Nov 07, 2022 at 08:17:10AM -0500, Mladen Gogala wrote: > On 11/7/22 06:19, Laurenz Albe wrote: > >Don't continue to work with that cluster even if everything seems OK now. > >"pg_dumpall" and restore to a new cluster on good hardware. > Why would that be necessary if the original machine

Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault

2022-11-07 Thread Stefan Froehlich
On Sun, Nov 06, 2022 at 09:48:32AM -0500, Tom Lane wrote: > Stefan Froehlich writes: > > | # create extension amcheck; > > | # select oid, relname from pg_class where relname ='faultytablename_pkey'; > > | [returns oid 537203] > > | # select bt_index_check(5

Re: server process (PID 2964738) was terminated by signal 11: Segmentation fault

2022-11-06 Thread Stefan Froehlich
On Sun, Nov 06, 2022 at 09:13:08AM -0500, Tom Lane wrote: > > | 2022-11-06 11:52:36.367 CET [2098-35] LOG: server process (PID 2964738) > > was terminated by signal 11: Segmentation fault > contrib/amcheck might help to identify the faulty data (at this > point there's reason to fear multiple c

server process (PID 2964738) was terminated by signal 11: Segmentation fault

2022-11-06 Thread Stefan Froehlich
This was starting with an invalid memory alloc request size, like in . I followed the suggestion to trace down the faulty record, found and fixed it. Now I can access that record again, but if I try to dump the table I get:

Re: unable to understand query result

2022-07-06 Thread Stefan Froehlich
On Wed, Jul 06, 2022 at 11:40:22AM +0200, Peter Eisentraut wrote: > On 06.07.22 11:31, Stefan Froehlich wrote: > >I have a database returing these result sets for two almost > >identical queries: > > > >#v+ > >$ select id, pid, length(pid), md5(pid) from pro

unable to understand query result

2022-07-06 Thread Stefan Froehlich
I have a database returing these result sets for two almost identical queries: #v+ $ select id, pid, length(pid), md5(pid) from product where pid like '800'; id | pid | length | md5 --+-++-- 3594 | 800 | 7 | 60