From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: Something fishy happening on frogmouth
Date: Wed, 30 Oct 2013 12:39:02 -0400
Message-ID: <4875.1383151142@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+TgmoaJkLK7ze6sczy2S9MxcCzTOLHw-2q1Si+VRqbVPuO4gw@mail.gmail.com>
References: <6557.1383073940@sss.pgh.pa.us>
<CA+Tgmob859sdnDuHAF31BE55qEoREnCzzWeqDbgkNB0d_F+zmA@mail.gmail.com>
<27889.1383139602@sss.pgh.pa.us>
<CA+TgmoaJkLK7ze6sczy2S9MxcCzTOLHw-2q1Si+VRqbVPuO4gw@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
Robert Haas <robertmhaas@gmail.com> writes:
> On Wed, Oct 30, 2013 at 9:26 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Also, why is the error "not enough space", rather than something about
>> a collision? And if this is the explanation, why didn't the previous
>> runs probing for allowable shmem size fail?
> Good questions. I think that my previous theory was wrong, and that
> the patch from Amit which I pushed a while ago should fix the
> breakage.
Indeed, I see frogmouth just went green, so Amit nailed it.
I'm still wondering why we try to create a DSM segment in bootstrap.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, robertmhaas@gmail.com, andrew@dunslane.net
Subject: Re: Something fishy happening on frogmouth
In-Reply-To: <4875.1383151142@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox