Re: Interface for pg_autovacuum - Mailing list pgsql-hackers

From Florian G. Pflug
Subject Re: Interface for pg_autovacuum
Date
Msg-id 458932FB.6030105@phlo.org
Whole thread Raw
In response to Interface for pg_autovacuum  ("Jim Nasby" <jim.nasby@enterprisedb.com>)
Responses Re: Interface for pg_autovacuum
List 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


pgsql-hackers by date:

Previous
From: Tom Dunstan
Date:
Subject: Re: effective_cache_size vs units
Next
From: Martijn van Oosterhout
Date:
Subject: Re: column ordering, was Re: [PATCHES] Enums patch v2