Re: Leftover reference to replacement selection 1 run case

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Leftover reference to replacement selection 1 run case
Date: 2017-12-13 00:37:40
Message-ID: CA+TgmoYPSGVQYgjEHL1dkQtFw5hzGqZd8_yMMtPYQX1jSh9Epw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 12, 2017 at 6:44 PM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Yes, you have that right. Per dumptuples(), even the zero tuple run edge
> case will still write a run marker, and will therefore still consume a tape.
> We must have at least two initial runs to merge. (though dummy runs for non
> final merges are a slightly different matter.)

OK, committed.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-12-13 00:54:52 Re: [HACKERS] Custom compression methods
Previous Message Ali Akbar 2017-12-13 00:26:52 Re: [HACKERS] pg_upgrade failed with error - ERROR: column "a" in child table must be marked NOT NULL