upstream/postgresql
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-04-13 21:17:00 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions
postgresql/src/backend/libpq
History
Tom Lane 6ccb2af725 Remove error report from pq_endmessage when pq_putmessage fails. The 
only possible failure is in pq_flush, which will log a (better!) report
anyway --- so pq_endmessage is just cluttering the log with a redundant
entry.  This matters when a client crashes partway through a large query,
since we will emit many broken-pipe reports before finishing the query
and exiting.
2001-04-16 01:46:57 +00:00
..
auth.c pgindent run. Make it all clean. 2001-03-22 04:01:46 +00:00
be-fsstubs.c pgindent run. Make it all clean. 2001-03-22 04:01:46 +00:00
crypt.c pgindent run. Make it all clean. 2001-03-22 04:01:46 +00:00
hba.c Restructure the key include files per recent pghackers discussion: there 2001-02-10 02:31:31 +00:00
Makefile Make the location of the Kerberos server key file run time configurable 2000-08-25 10:00:35 +00:00
password.c pgindent run. Make it all clean. 2001-03-22 04:01:46 +00:00
pg_hba.conf.sample Improve comments in pg_hba.conf.sample and the associated SGML 2000-11-21 20:44:32 +00:00
pg_ident.conf.sample Improve comments. 2000-11-21 20:48:38 +00:00
pqcomm.c pgindent run. Make it all clean. 2001-03-22 04:01:46 +00:00
pqformat.c Remove error report from pq_endmessage when pq_putmessage fails. The 2001-04-16 01:46:57 +00:00
pqpacket.c pgindent run. Make it all clean. 2001-03-22 04:01:46 +00:00
pqsignal.c pgindent run. Make it all clean. 2001-03-22 04:01:46 +00:00
README.SSL Add README.SSL 1999-09-27 03:16:09 +00:00
util.c Change Copyright from PostgreSQL, Inc to PostgreSQL Global Development Group. 2001-01-24 19:43:33 +00:00

README.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