| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE lock strength reduction patch is unsafe |
| Date: | 2011-06-20 23:03:00 |
| Message-ID: | BANLkTinmADCTafq4Ko-aYep-MtG+Eu-_xQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 20, 2011 at 11:55 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> I agree we shouldn't do anything about the name lookups for 9.1
> That is SearchCatCache using RELNAMENSP lookups, to be precise, as
> well as triggers and few other similar call types.
Name lookups give ERRORs that look like this...
relation "pgbench_accounts" does not exist
>> The ALTER TABLE patch
>> has greatly expanded the scope of the issue, and that *is* a regression
>> compared to prior releases.
>
> I agree the scope for RELOID errors increased with my 9.1 patch.
Which originally generated ERRORs like
cache lookup failed for relation 16390
or
could not open relation with OID 16390
which should now be absent from the server log.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brendan Jurd | 2011-06-21 00:06:39 | Re: Fwd: Keywords in pg_hba.conf should be field-specific |
| Previous Message | Simon Riggs | 2011-06-20 22:55:35 | Re: ALTER TABLE lock strength reduction patch is unsafe |