Re: Getting rid of "unknown error" in dblink and postgres_fdw

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Getting rid of "unknown error" in dblink and postgres_fdw
Date: 2016-12-21 16:55:23
Message-ID: CAKFQuwYUTXOfGsxCmWHVOB8hFOoW1uvJDGh5k1GLSGaUmKuC+Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 21, 2016 at 9:49 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> A possible objection is that if we really are on the hairy edge of OOM,
> trying to construct such error strings might push us over the edge

What am I missing here? Constructing said string occurs on the local end
of the connection but the memory problem exists on the remote end.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-12-21 16:56:52 Re: Getting rid of "unknown error" in dblink and postgres_fdw
Previous Message Robert Haas 2016-12-21 16:55:00 Re: multi-level partitions and partition-wise joins