postgres

History

Heikki Linnakangas 40f908bdcd Introduce Streaming Replication. This includes two new kinds of postmaster processes, walsenders and walreceiver. Walreceiver is responsible for connecting to the primary server and streaming WAL to disk, while walsender runs in the primary server and streams WAL from disk to the client. Documentation still needs work, but the basics are there. We will probably pull the replication section to a new chapter later on, as well as the sections describing file-based replication. But let's do that as a separate patch, so that it's easier to see what has been added/changed. This patch also adds a new section to the chapter about FE/BE protocol, documenting the protocol used by walsender/walreceivxer. Bump catalog version because of two new functions, pg_last_xlog_receive_location() and pg_last_xlog_replay_location(), for monitoring the progress of replication. Fujii Masao, with additional hacking by me		16 years ago
..
Makefile	Refactor backend makefiles to remove lots of duplicate code	18 years ago
README.SSL	Remove large parts of the old SSL readme, that consisted of a couple	17 years ago
auth.c	Create typedef pgsocket for storing socket descriptors.	16 years ago
be-fsstubs.c	Update copyright for the year 2010.	16 years ago
be-secure.c	Introduce Streaming Replication.	16 years ago
crypt.c	Update copyright for the year 2010.	16 years ago
hba.c	Introduce Streaming Replication.	16 years ago
ip.c	Create typedef pgsocket for storing socket descriptors.	16 years ago
md5.c	Update copyright for the year 2010.	16 years ago
pg_hba.conf.sample	Introduce Streaming Replication.	16 years ago
pg_ident.conf.sample	Improve comments in pg_ident.conf.sample.	17 years ago
pqcomm.c	Introduce Streaming Replication.	16 years ago
pqformat.c	Remove all the special-case code for INT64_IS_BUSTED, per decision that	16 years ago
pqsignal.c	Update copyright for the year 2010.	16 years ago

README.SSL

$PostgreSQL: pgsql/src/backend/libpq/README.SSL,v 1.7 2008/10/24 11:48:29 mha Exp $

SSL
===

>From the servers perspective:


  Receives StartupPacket
           |
           |
 (Is SSL_NEGOTIATE_CODE?) -----------  Normal startup
           |                  No
           |
           | Yes
           |
           |
 (Server compiled with USE_SSL?) ------- Send 'N'
           |                       No        |
           |                                 |
           | Yes                         Normal startup
           |
           |
        Send 'S'
           |
           |
      Establish SSL
           |
           |
      Normal startup
     




>From the clients perspective (v6.6 client _with_ SSL):


      Connect
         |
         |
  Send packet with SSL_NEGOTIATE_CODE
         |
         |
  Receive single char  ------- 'S' -------- Establish SSL
         |                                       |
         | '<else>'                              |
         |                                  Normal startup
         |
         |
   Is it 'E' for error  ------------------- Retry connection
         |                  Yes             without SSL
         | No
         |
   Is it 'N' for normal ------------------- Normal startup
         |                  Yes
         |
   Fail with unknown

---------------------------------------------------------------------------