Re: [HACKERS] LONG varsize - how to go on - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] LONG varsize - how to go on
Date
Msg-id 199912180613.BAA11773@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] LONG varsize - how to go on  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses pgindent (Re: [HACKERS] LONG varsize - how to go on)
Re: [HACKERS] LONG varsize - how to go on
List 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@candle.pha.pa.us            |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Keith Parks
Date:
Subject: RE: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
Next
From: Mike Mascari
Date:
Subject: SPI header dependencies