Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL

From: Taral <taral(at)taral(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Chris <chris(at)bitmead(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org, pgsql-sql(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
Date: 2000-02-03 16:50:30
Message-ID: Pine.LNX.4.10.10002031049570.6100-100000@r149127-2815.dobiecenter.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackerspgsql-sql
On Thu, 3 Feb 2000, Tom Lane wrote:

> Maintaining an accurate count of descendants (or indexes for that
> matter) would be expensive; in particular, it'd create severe
> concurrency problems.

What about fixing these things on VACUUM then?

Taral


In response to

Responses

pgsql-hackers by date

Next:From: Peter MountDate: 2000-02-03 16:51:33
Subject: RE: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
Previous:From: Thomas LockhartDate: 2000-02-03 16:43:51
Subject: Parser/planner and column aliases

pgsql-sql by date

Next:From: Peter MountDate: 2000-02-03 16:51:33
Subject: RE: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
Previous:From: Peter EisentrautDate: 2000-02-03 16:43:43
Subject: Re: [SQL] INSTALL doc correction ...

pgsql-general by date

Next:From: Tom LaneDate: 2000-02-03 16:52:58
Subject: Re: [HACKERS] Re: [SQL] Proposed Changes to PostgreSQL
Previous:From: Peter EisentrautDate: 2000-02-03 16:26:50
Subject: Re: [HACKERS] Proposed Changes to PostgreSQL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group