From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Fix for OWNER TO breaking ACLs |
Date: | 2004-08-02 05:01:31 |
Message-ID: | 1064.1091422891@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
>> The way you had it coded, it was generating
>> new index entries pointing at the old version of the tuple ...
> Strange. I guess I must have been testing with a database that had
> short enough system catalogs that the indexes were never used?
Could be, especially if you were using client-side queries to check the
result. I think most of the system's internal catalog fetches are
hard-wired to use indexes except under the most dire circumstances
(mainly, a standalone backend with -P). But a client-issued query
would do whatever the planner thought best.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2004-08-02 06:19:12 | Re: UTF8 for all translations? |
Previous Message | Christopher Kings-Lynne | 2004-08-02 04:33:37 | Re: USING INDEX TABLESPACE |