[HACKERS] Regression caused by recent change to initdb?

Hi, I stumbled upon a possibly strange behavior which may be related to recent initdb changes. For a freshly initdb'd cluster, the following looks fishy: postgres=# SELECT relname, relnamespace::regnamespace FROM pg_class WHERE relnamespace != 'pg_catalog'::regnamespace AND relnamespace !=

Re: [HACKERS] Regression caused by recent change to initdb?

On 2016/01/06 17:32, Amit Langote wrote: > Hi, > > I stumbled upon a possibly strange behavior which may be related to recent > initdb changes. For a freshly initdb'd cluster, the following looks fishy: > > postgres=# SELECT relname, relnamespace::regnamespace FROM pg_class > WHERE relnamespace

Re: [HACKERS] Regression caused by recent change to initdb?

Amit Langote writes: > On 2016/01/06 17:32, Amit Langote wrote: >> I stumbled upon a possibly strange behavior which may be related to recent >> initdb changes. For a freshly initdb'd cluster, the following looks fishy: >> ... >> These seem to be leftovers of

Re: [HACKERS] Regression caused by recent change to initdb?

On 2016/01/06 23:50, Tom Lane wrote: > Amit Langote writes: >> On 2016/01/06 17:32, Amit Langote wrote: >>> I stumbled upon a possibly strange behavior which may be related to recent >>> initdb changes. For a freshly initdb'd cluster, the following looks fishy: >>>