| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | The Hermit Hacker <scrappy(at)hub(dot)org>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_group_name_index corrupt? |
| Date: | 2000-05-05 06:02:58 |
| Message-ID: | 5425.957506578@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
>> Done and done. I also realized that pg_upgrade had another nasty bug
>> in it: the VACUUMs were not necessarily executed as superuser, but as
>> whichever user happened to own the item dumped last by pg_dump in each
>> database. That would result in VACUUM skipping over tables it thought
>> it didn't have permission to vacuum --- like, say, all the system
>> tables. Perhaps this explains the failures that some people have
>> reported.
>>
>> Another day, another bug swatted ...
> Yes, good eye. Thanks.
BTW, I believe that this was actually a bug I created --- in prior
releases VACUUM would happily vacuum anything in sight, whether you
had privileges to lock the target tables or not. So pg_upgrade didn't
have to worry before. But it does now...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-05-05 06:07:29 | Re: 7.0RC2 compile error ! |
| Previous Message | Tom Lane | 2000-05-05 05:49:41 | Re: ``..Advice For New Immigrants... |