Re: 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 != 'pg_catalog'::regnamespace
> AND relnamespace != 'pg_toast'::regnamespace
> AND relnamespace != 'information_schema'::regnamespace;
>        relname        |  relnamespace
> ----------------------+-----------------
>  pg_toast_11817       | pg_toast_temp_1
>  pg_toast_11817_index | pg_toast_temp_1
>  pg_toast_11822       | pg_toast_temp_1
>  pg_toast_11822_index | pg_toast_temp_1
>  pg_toast_11827       | pg_toast_temp_1
>  pg_toast_11827_index | pg_toast_temp_1
>  tmp_pg_description   | pg_temp_1
>  tmp_pg_shdescription | pg_temp_1
>  tmp_pg_collation     | pg_temp_1
> (10 rows)
> 
> These seem to be leftovers of activities of initdb.c's setup_description()
> and setup_collaction().

I noticed these leftovers are not present in template1.

Thanks,
Amit