Re: [HACKERS] Non-transactional pg_class, try 2

2006-06-26 Thread Alvaro Herrera
Tom Lane wrote: > Alvaro Herrera <[EMAIL PROTECTED]> writes: > > What I'm after is not freezing for read-only media, nor archive, nor > > read-only tables. What I'm after is removing the requirement that all > > databases must be vacuumed wholly every 2 billion transactions. > > Well, if that's t

Re: [HACKERS] non-transactional pg_class

2006-05-29 Thread Tom Lane
Alvaro Herrera <[EMAIL PROTECTED]> writes: > I've been taking a look at what's needed for the non-transactional part > of pg_class. If I've understood this correctly, we need a separate > catalog, which I've dubbed pg_ntclass (better ideas welcome), and a new > pointer in RelationData to hold a po

[HACKERS] non-transactional pg_class

2006-05-28 Thread Alvaro Herrera
Hi, I've been taking a look at what's needed for the non-transactional part of pg_class. If I've understood this correctly, we need a separate catalog, which I've dubbed pg_ntclass (better ideas welcome), and a new pointer in RelationData to hold a pointer to this new catalog for each relation.