Re: [PATCH] Windows port, fix some resources leaks - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [PATCH] Windows port, fix some resources leaks
Date
Msg-id CA+Tgmoap7x9F3XPprvq7AZbT9AhzxcP5ae-PHFSSjiH+cZHuLw@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Windows port, fix some resources leaks  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [PATCH] Windows port, fix some resources leaks  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Tue, Jan 28, 2020 at 4:06 PM Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> I don't think we have ever expressed it as such, but certainly we prefer
> postmaster to be super robust ... rather live with a some hundred bytes
> leak rather than have it die and take the whole database service down
> for what's essentially a fringe bug that has bothered no one in a decade
> and a half.

Well, yeah. I mean, I'm not saying it's a good idea in this instance
to FATAL here. I'm just saying that I don't think there is a general
rule that code which does FATAL in the postmaster is automatically
wrong, which is what I took Michael to be suggesting.

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



pgsql-hackers by date:

Previous
From: Ranier Vilela
Date:
Subject: Re: [PATCH] Windows port, fix some resources leaks
Next
From: Tom Lane
Date:
Subject: Re: Removing pg_pltemplate and creating "trustable" extensions