Hi all,
> Also, in addition to the objections you noted, there's the problem that
> this change requires changing logging_collector to default to "on".
> That's an *enormous* compatibility break, because of the effects on
> where the log output goes.
>
As a consultant with so many customers that
>
>
> I'm wondering where the choice of the name "heap" originally came from
> and what it refers to.
It seems to me that "heap" is an Oracle word (as explained here[1]).
> By default, a table is organized as a heap, which means that the database
places rows where they fit best rather than in a
> > On Tue, Jan 08, 2019 at 04:42:35PM +0900, Michael Paquier wrote:
> >> I can see your point, though I would stick with
> >> ERRCODE_WRONG_OBJECT_TYPE for consistency with the existing code and
> >> because the code is intended to not work on anything else than plain
> >> tables, at least now.
>
