Re: Pre-forking backend, an idea

From: mlw <markw(at)mohawksoft(dot)com>
To:
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pre-forking backend, an idea
Date: 2001-10-15 16:37:50
Message-ID: 3BCB10DE.941276CE@mohawksoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I was just combing through an Oracle control file, it occured to me that a
pre-forking Postgres could be designed to work similar to Oracle.

Oracle has a listener keyed to an IP port. The instance of the listener is
configured to listen for a particular database instance. This may be a bit
flakey, but hear me out here. This would be similar to having Postgres listen on
different ports.

A single Postgres instance can start and run as it does now, but it can also be
configured to prefork "listeners" for specified databases on different ports.
That way you do not need the main postgres instance to be able to pass the socket
to the forked child. Also, in the configuration files for the "listeners" you
could also specify Postgres settings for each database.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-10-15 16:42:06 Ready for Beta?
Previous Message Marc G. Fournier 2001-10-15 16:11:35 Re: Snaptshot appears fine to me ...