TODO item for pg_ctl and server detection

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: TODO item for pg_ctl and server detection
Date: 2010-12-24 14:58:50
Message-ID: 201012241458.oBOEwoR11746@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

While I am working on pg_ctl, I saw this TODO item:

Have the postmaster write a random number to a file on startup that
pg_ctl checks against the contents of a pg_ping response on its initial
connection (without login)

This will protect against connecting to an old instance of the
postmaster in a different or deleted subdirectory.

http://archives.postgresql.org/pgsql-bugs/2009-10/msg00110.php
http://archives.postgresql.org/pgsql-bugs/2009-10/msg00156.php

Based on our new PQPing(), do we ever want to implement this or should I
remove the TODO item? It seems this would require a server connection,
which is something we didn't want to force pg_ctl -w to do in case
authentication is broken.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2010-12-24 15:52:50 Re: WIP patch for parallel pg_dump
Previous Message Bruce Momjian 2010-12-24 14:47:49 Re: pg_ctl and port number detection