Postgres Pro
Downloads
Home   >   mailing lists

Re: Printing bitmap objects in the debugger - Mailing list pgsql-hackers

From Amit Langote
Subject Re: Printing bitmap objects in the debugger
Date
Msg-id 90fa1659-0c51-9bce-1bbb-f5cfa2eabf1b@lab.ntt.co.jp
Whole thread Raw
In response to Re: Printing bitmap objects in the debugger  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Printing bitmap objects in the debugger
List pgsql-hackers
Tree view 
On 2016/09/15 0:04, Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.com> writes:
>> I don't understand.  Why don't you just use "call pprint(the bitmapset)"
>> in the debugger?
> 
> Bitmapsets aren't Nodes, so pprint doesn't work directly on them.
> I usually find that I can pprint some node containing the value(s)
> I'm interested in, but maybe that isn't working for Ashutosh's
> particular case.

There are many loose (ie, not inside any Node) Relids variables within the
optimizer code.  Perhaps Ashutosh ended up needing to look at those a lot.

Thanks,
Amit

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pg_basebackup, pg_receivexlog and data durability (was: silent data loss with ext4 / all current versions)
Next
From: Michael Paquier
Date:
Subject: Re: pg_basebackup, pg_receivexlog and data durability (was: silent data loss with ext4 / all current versions)