| From: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
|---|---|
| To: | Jim Nasby <jim(dot)nasby(at)enterprisedb(dot)com> |
| Cc: | PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Interface for pg_autovacuum |
| Date: | 2006-12-20 12:56:27 |
| Message-ID: | 458932FB.6030105@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim Nasby wrote:
> I'm teaching a class this week and a student asked me about OIDs. He
> related the story of how in Sybase, if you moved a database from one
> server from another, permissions got all screwed up because user IDs no
> longer matched. I explained that exposing something like an integer ID
> in a user interface or an API is just a bad idea and PostgreSQL doesn't
> do that.
>
> Then I got to pg_autovacuum....
>
> So... is there any reason there isn't a prescribed interface to
> pg_autovacuum that doesn't expose vacrelid? Can we get that added to TODO?
Wouldn't it be sufficient to change the type of vacrelid from oid
to regclass? Then just dumping and restoring pg_autovacuum like any
other table should Just Work.
greetings, Florian Pflug
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2006-12-20 13:17:49 | VS: Companies Contributing to Open Source |
| Previous Message | Felipe Rondon Rocha | 2006-12-20 12:43:52 | Fw: Fw: choosing use an index or not |