Re: slow queries over information schema.tables

From: Greg Stark <stark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: slow queries over information schema.tables
Date: 2018-12-21 18:46:55
Message-ID: CAM-w4HMuwG3NdyphOt1k_+QUPPv-y9Quc3caytUNNA7LcVQjbg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Just brainstorming here. Another crazy idea would be to get rid of
"name" data type, at least from the user-visible planner point of
view. It would probably have to be stored as a fixed length data type
like today but with a one-byte length header. That would make it
possible for the planner to use as if it was just another varchar.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Fetter 2018-12-21 18:56:22 Compiling on Termux
Previous Message Kumar, Virendra 2018-12-21 18:39:28 RE: Query planner / Analyse statistics bad estimate rows=1 with maximum statistics 10000 on PostgreSQL 10.2