Re: [HACKERS] Cache lookup errors with functions manipulation object addresses

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Cache lookup errors with functions manipulation object addresses
Date: 2018-01-12 00:45:19
Message-ID: CAEepm=2qAZrn324kXa8mEUbOiRxYG_iyjguGg3uhC7LjU+hJqQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 27, 2017 at 1:01 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Fri, Nov 24, 2017 at 9:13 PM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>> Attached is a rebased patch set. Álvaro, as you have introduced most
>> of the problems with 4464303 & friends dated of 2015 when you
>> introduced get_object_address(), could you look at this patch set?

Hi Michael,

FYI:

func.sgml:17550: parser error : Opening and ending tag mismatch:
literal line 17550 and unparseable
<literal>NULL</> values for undefined objects.
^
func.sgml:17567: parser error : Opening and ending tag mismatch:
literal line 17567 and unparseable
with <literal>NULL</> values.
^
func.sgml:17582: parser error : Opening and ending tag mismatch:
literal line 17582 and unparseable
Undefined objects are identified with <literal>NULL</> values.
^
func.sgml:20721: parser error : chunk is not well balanced
postgres.sgml:105: parser error : Failure to process entity func
&func;
^
postgres.sgml:105: parser error : Entity 'func' not defined
&func;
^

--
Thomas Munro
http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-01-12 00:48:58 Re: [HACKERS] PATCH: multivariate histograms and MCV lists
Previous Message Tatsuro Yamada 2018-01-12 00:42:21 Re: Minor code improvement to estimate_path_cost_size in postgres_fdw