| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | <pokurev(at)pm(dot)nttdata(dot)co(dot)jp>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Amit Langote <amitlangote09(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, <bannos(at)nttdata(dot)co(dot)jp> |
| Subject: | Re: [PROPOSAL] VACUUM Progress Checker. |
| Date: | 2016-03-12 16:56:00 |
| Message-ID: | 56E44A20.4000003@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/10/16 7:48 AM, Robert Haas wrote:
> I think the problem is that you can't show the name of a non-global
> SQL object (such as a relation) unless the object is in the current
> database. Many of the views in the first group are database-local
> views, while things like pg_locks span all databases. We can show the
> datid/relid always, but if we have a relname column it will have to be
> NULL unless the datid is our database.
I would prefer that if the object is in another database we at least
display the OID. That way, if you're logging this info you can go back
later and figure out what was going on.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-03-12 16:56:24 | Re: [COMMITTERS] pgsql: Only try to push down foreign joins if the user mapping OIDs mat |
| Previous Message | Tom Lane | 2016-03-12 16:38:41 | Re: Perl's newSViv() versus 64-bit ints? |