On Tue, Feb 11, 2020 at 8:33 PM Peter Geoghegan wrote:
>
> On Sun, Feb 9, 2020 at 12:50 PM Colin Adler wrote:
> > Looks like it found something. I checked out the contrib/pageinspect docs
> > but
> > wasn't too sure what to run. Are incompatible libc versions causing btree
> > corruption
On Sun, Feb 9, 2020 at 12:50 PM Colin Adler wrote:
> Looks like it found something. I checked out the contrib/pageinspect docs but
> wasn't too sure what to run. Are incompatible libc versions causing btree
> corruption something you consider a bug? If it's something you'd like to look
> into
Peter,
Thanks for taking the time to respond and hope you're having a good
weekend. My
apologies for not noting the Postgres version. I thought about it after I
sent
the email but I didn't want to spam the thread.
$ psql --version
psql (PostgreSQL) 11.6
One interesting thing you mention is that
On Fri, Feb 7, 2020 at 3:52 PM Colin Adler wrote:
> Seems to work now. My question is, is this something I should report to the
> maintainers?
I am one of the people that maintains the B-Tree code.
You didn't mention what version of Postgres you're using here. That
could be important. Please
Hi all,
Earlier today we were trying to debug why a row wasn't being deleted from a
table and we ran into some interesting behavior.
This is the table in question:
coder=# \d+ extensions
Table "public.extensions"
Column | Type | Collation | Nullable | Default
|
