pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Васильев Дмитрий <d.vasilyev@postgrespro.ru>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Performance degradation in commit ac1d794
Date: Fri, 25 Dec 2015 16:29:53 -0500
Message-ID: <24833.1451078993@sss.pgh.pa.us> (raw)
In-Reply-To: <20151225211326.z4umuafvv27nczya@alap3.anarazel.de>
References: <CAB-SwXZh44_2ybvS5Z67p_CDz=XFn4hNAD=CnMEF+QqkXwFrGg@mail.gmail.com>
	<EA5F5A26-2E66-4CAB-B3EC-EAD65501B74B@anarazel.de>
	<CAB-SwXZ+6==ZmGvME9vKtUExaQuYYf6oRUNBjkg5SYqv267dUQ@mail.gmail.com>
	<9F7A592C-323B-40CF-AEB6-20D28EAEFFDD@anarazel.de>
	<CAB-SwXb1p6W-_Qrd=h=c47Tv1DuWJwLYNWyq8j9g2yRp4ye-BQ@mail.gmail.com>
	<19322.1451067023@sss.pgh.pa.us>
	<CEAB3A3D-FD33-4AB9-BDD3-FC0E20776245@anarazel.de>
	<19834.1451068135@sss.pgh.pa.us>
	<20151225211326.z4umuafvv27nczya@alap3.anarazel.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

Andres Freund <andres@anarazel.de> writes:
> There's a couple solutions I can think of to that problem:
> 1) Use epoll()/kqueue, or other similar interfaces that don't require
>    re-registering fds at every invocation. My guess is that that'd be
>    desirable for performance anyway.

Portability, on the other hand, would be problematic.

> 2) Create a pair of fds between postmaster/backend for each
>    backend. While obviously increasing the the number of FDs noticeably,
>    it's interesting for other features as well: If we ever want to do FD
>    passing from postmaster to existing backends, we're going to need
>    that anyway.

Maybe; it'd provide another limit on how many backends we could run.

> 3) Replace the postmaster_alive_fds socketpair by some other signalling
>    mechanism. E.g. sending a procsignal to each backend, which sets the
>    latch and a special flag in the latch structure.

And what would send the signal?  The entire point here is to notice the
situation where the postmaster has crashed.  It can *not* depend on the
postmaster taking some action.

			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



view thread (93+ messages)  latest in thread

Message-ID: <24833.1451078993@sss.pgh.pa.us>
Permalink:  ../24833.1451078993@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/24833.1451078993@sss.pgh.pa.us

 · 

reply
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, andres@anarazel.de, d.vasilyev@postgrespro.ru
  Subject: Re: Performance degradation in commit ac1d794
  In-Reply-To: <24833.1451078993@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