Re: [HACKERS] LONG varsize - how to go on

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jan Wieck <wieck(at)debis(dot)com>, PostgreSQL HACKERS <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] LONG varsize - how to go on
Date: 1999-12-18 06:13:31
Message-ID: 199912180613.BAA11773@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> It seems like what we ought to be doing in the near term is finishing
> up the loose ends that remain with table locking, cache invalidation,
> etc. The recently reported "LockRelease" errors seem to fall into
> that category as well. Anyway, my point is we ought to go full steam
> ahead into cleanup-and-make-ready-for-release mode. Dare I suggest
> that we should declare feature freeze *now*, and concentrate on bug
> fixes only for the next six weeks? If not, what features are on the
> near horizon?
>
> If Bruce wants to run pgindent before the Feb release, maybe the easiest
> answer is to do it now (in the next few days) and then Jan can start
> working on his new stuff without worrying about it.

I don't need to run pgindent before _every_ release. No problem.

I don't see Jan's work chaning what the rest of us focus on. Let's see
how it goes. I certainly don't have anything planned.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 1999-12-18 13:06:28 Re: [HACKERS] psql vs. gcc
Previous Message Keith Parks 1999-12-18 06:07:31 RE: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock