Thread

  1. pid file for postmaster?

    Tatsuo Ishii <t-ishii@sra.co.jp> — 1999-11-24T06:11:59Z

    Hi,
    
    It would be nice if postmaster has its own pid file to send signals to
    it. I think the pid file could be placed under $PGDATA. Opinions?
    --
    Tatsuo Ishii
    
    
  2. Re: [HACKERS] pid file for postmaster?

    Tom Lane <tgl@sss.pgh.pa.us> — 1999-11-24T06:33:37Z

    Tatsuo Ishii <t-ishii@sra.co.jp> writes:
    > It would be nice if postmaster has its own pid file to send signals to
    > it. I think the pid file could be placed under $PGDATA. Opinions?
    
    Yes, that's been discussed before, and I think it's even got an entry
    on the TODO list.  If you've got time to tackle it now, great!
    
    $PGDATA seems like the right place to put the file, since we can only
    have one active postmaster at a time in a database directory.
    
    I assume you'll also create a script that sends SIGTERM or other
    requested signal to the postmaster, using this file?
    
    			regards, tom lane
    
    
  3. Re: [HACKERS] pid file for postmaster?

    Tatsuo Ishii <t-ishii@sra.co.jp> — 1999-11-24T06:38:31Z

    From: Tom Lane <tgl@sss.pgh.pa.us>
    > Tatsuo Ishii <t-ishii@sra.co.jp> writes:
    > > It would be nice if postmaster has its own pid file to send signals to
    > > it. I think the pid file could be placed under $PGDATA. Opinions?
    > 
    > Yes, that's been discussed before, and I think it's even got an entry
    > on the TODO list.  If you've got time to tackle it now, great!
    > 
    > $PGDATA seems like the right place to put the file, since we can only
    > have one active postmaster at a time in a database directory.
    
    Right.
    
    > I assume you'll also create a script that sends SIGTERM or other
    > requested signal to the postmaster, using this file?
    
    Of course:-) I'm thinking about to make an apachectl-like script.
    --
    Tatsuo Ishii
    
    
  4. Re: [HACKERS] pid file for postmaster?

    Michael Meskes <meskes@postgresql.org> — 1999-11-25T07:20:33Z

    On Wed, Nov 24, 1999 at 01:33:37AM -0500, Tom Lane wrote:
    > > it. I think the pid file could be placed under $PGDATA. Opinions?
    > ... 
    > $PGDATA seems like the right place to put the file, since we can only
    > have one active postmaster at a time in a database directory.
    
    Ehem, I think the correct place would be /var/run. At least that's what the
    filesystem standard says IIRC.
    
    Michael
    -- 
    Michael Meskes                         | Go SF 49ers!
    Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
    Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
    Email: Michael@Fam-Meskes.De           | Use PostgreSQL!
    
    
  5. Re: [HACKERS] pid file for postmaster?

    Tim Holloway <mtsinc@southeast.net> — 1999-11-25T13:19:45Z

    Red Hat ALREADY creates a file "postmaster.pid" in the /var/lock directory.
    I don't know how far the /var/lock convention goes across different platforms,
    but I recommend using IT or its equivalent, I still have scars from my OS/2
    days where every product put its goodies in a different place and you had to
    guess where, how, and in what format.
    
        Regards,
          Tim Holloway
    
    Tatsuo Ishii wrote:
    > 
    > From: Tom Lane <tgl@sss.pgh.pa.us>
    > > Tatsuo Ishii <t-ishii@sra.co.jp> writes:
    > > > It would be nice if postmaster has its own pid file to send signals to
    > > > it. I think the pid file could be placed under $PGDATA. Opinions?
    > >
    > > Yes, that's been discussed before, and I think it's even got an entry
    > > on the TODO list.  If you've got time to tackle it now, great!
    > >
    > > $PGDATA seems like the right place to put the file, since we can only
    > > have one active postmaster at a time in a database directory.
    > 
    > Right.
    > 
    > > I assume you'll also create a script that sends SIGTERM or other
    > > requested signal to the postmaster, using this file?
    > 
    > Of course:-) I'm thinking about to make an apachectl-like script.
    > --
    > Tatsuo Ishii
    > 
    > ************
    
    
  6. Re: [HACKERS] pid file for postmaster?

    Bruce Momjian <pgman@candle.pha.pa.us> — 1999-11-25T18:35:14Z

    > Red Hat ALREADY creates a file "postmaster.pid" in the /var/lock directory.
    > I don't know how far the /var/lock convention goes across different platforms,
    > but I recommend using IT or its equivalent, I still have scars from my OS/2
    > days where every product put its goodies in a different place and you had to
    > guess where, how, and in what format.
    
    Problem with that it is going to require root permission to create that
    file or directory if it doesn't exist.  I think we have to put it in the
    pgsql/data directory.  Sorry.
    
    -- 
      Bruce Momjian                        |  http://www.op.net/~candle
      maillist@candle.pha.pa.us            |  (610) 853-3000
      +  If your life is a hard drive,     |  830 Blythe Avenue
      +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
    
    
  7. Re: [HACKERS] pid file for postmaster?

    Hannu Krosing <hannu@tm.ee> — 1999-11-25T19:38:09Z

    Michael Meskes wrote:
    > 
    > On Wed, Nov 24, 1999 at 01:33:37AM -0500, Tom Lane wrote:
    > > > it. I think the pid file could be placed under $PGDATA. Opinions?
    > > ...
    > > $PGDATA seems like the right place to put the file, since we can only
    > > have one active postmaster at a time in a database directory.
    > 
    > Ehem, I think the correct place would be /var/run. At least that's what the
    > filesystem standard says IIRC.
    
    But that forces us to distinguish between several running backends, with the 
    main aim of _not_ allowing two distinct backends to be run from the same 
    $PGDATA.
    
    we could of course start naming them like /var/run/pgsql.pid.for.var.lib.pgsql
    
    ------------
    Hannu
    
    
  8. Re: [HACKERS] pid file for postmaster?

    Michael Meskes <meskes@postgresql.org> — 1999-11-25T20:05:46Z

    On Thu, Nov 25, 1999 at 09:38:09PM +0200, Hannu Krosing wrote:
    > But that forces us to distinguish between several running backends, with the 
    > main aim of _not_ allowing two distinct backends to be run from the same 
    > $PGDATA.
    
    Oops. It seems I did not completely read that mail.
    
    > we could of course start naming them like /var/run/pgsql.pid.for.var.lib.pgsql
    
    Does not make sense IMO.
    
    Michael
    -- 
    Michael Meskes                         | Go SF 49ers!
    Th.-Heuss-Str. 61, D-41812 Erkelenz    | Go Rhein Fire!
    Tel.: (+49) 2431/72651                 | Use Debian GNU/Linux!
    Email: Michael@Fam-Meskes.De           | Use PostgreSQL!
    
    
  9. Re: [HACKERS] pid file for postmaster?

    Dmitry Samersoff <dms@wplus.net> — 1999-11-25T20:13:06Z

    On 25-Nov-99 Michael Meskes wrote:
    > On Wed, Nov 24, 1999 at 01:33:37AM -0500, Tom Lane wrote:
    >> > it. I think the pid file could be placed under $PGDATA. Opinions?
    >> ... 
    >> $PGDATA seems like the right place to put the file, since we can only
    >> have one active postmaster at a time in a database directory.
    > 
    > Ehem, I think the correct place would be /var/run. At least that's what the
    > filesystem standard says IIRC.
    
    I agree ...
    
    
    
    ---
    Dmitry Samersoff, dms@wplus.net, ICQ:3161705
    http://devnull.wplus.net
    * There will come soft rains ...
    
    
  10. Re: [HACKERS] pid file for postmaster?

    Tim Holloway <mtsinc@southeast.net> — 1999-11-25T21:51:58Z

    Just playing Devil's Advocate.
    
    Having to have root persmission to set up a system is more the rule than the exception,
    though. Under Windows NT, for example, you can't create the registry keys except as
    an administrator, even though unprivileged users will be setting the values.
    Considering what having major DBMS installed could do to the system load, one could
    even argue that ONLY an administrator should be allowed to install it!
    
    But that's another issue entirely.....
    
    Bruce Momjian wrote:
    > 
    > > Red Hat ALREADY creates a file "postmaster.pid" in the /var/lock directory.
    > > I don't know how far the /var/lock convention goes across different platforms,
    > > but I recommend using IT or its equivalent, I still have scars from my OS/2
    > > days where every product put its goodies in a different place and you had to
    > > guess where, how, and in what format.
    > 
    > Problem with that it is going to require root permission to create that
    > file or directory if it doesn't exist.  I think we have to put it in the
    > pgsql/data directory.  Sorry.
    > 
    > --
    >   Bruce Momjian                        |  http://www.op.net/~candle
    >   maillist@candle.pha.pa.us            |  (610) 853-3000
    >   +  If your life is a hard drive,     |  830 Blythe Avenue
    >   +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
    
    
  11. Re: [HACKERS] pid file for postmaster?

    Bruce Momjian <pgman@candle.pha.pa.us> — 1999-11-26T04:02:57Z

    [Charset KOI8-R unsupported, filtering to ASCII...]
    > 
    > On 25-Nov-99 Michael Meskes wrote:
    > > On Wed, Nov 24, 1999 at 01:33:37AM -0500, Tom Lane wrote:
    > >> > it. I think the pid file could be placed under $PGDATA. Opinions?
    > >> ... 
    > >> $PGDATA seems like the right place to put the file, since we can only
    > >> have one active postmaster at a time in a database directory.
    > > 
    > > Ehem, I think the correct place would be /var/run. At least that's what the
    > > filesystem standard says IIRC.
    > 
    > I agree ...
    > 
    
    I think the idea was to put the file in /data, and symlink to /tmp or
    /var/run.
    
    -- 
      Bruce Momjian                        |  http://www.op.net/~candle
      maillist@candle.pha.pa.us            |  (610) 853-3000
      +  If your life is a hard drive,     |  830 Blythe Avenue
      +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026