Features .......................................................................................1326 E.6.4. Changes ......................................................................................... ...1430 E.52. Release 6.4 ................................................................................................................1430 E.52.1. Migration to version 6.4 ...................... PGconn structure because they are subject to change in the future. (Beginning in PostgreSQL release 6.4, the definition of the struct behind PGconn is not even provided in libpq-fe.h. If you have old code

...1307 E.39. Release 6.4 ................................................................................................................1308 E.39.1. Migration to version 6.4 ...................... PGconn structure because they are subject to change in the future. (Beginning in PostgreSQL release 6.4, the definition of the struct behind PGconn is not even provided in libpq-fe.h. If you have old code present, the extra field is unused and will always point to an empty string.) Note: In PostgreSQL 6.4 and later, the be_pid is that of the notifying server process, whereas in earlier versions it was always

......1223 E.39. Release 6.4 .........................................................................................................1224 E.39.1. Migration to version 6.4 .......................... PGconn structure because they are subject to change in the future. (Beginning in PostgreSQL release 6.4, the definition of the struct behind PGconn is not even provided in libpq-fe.h. If you have old code present, the extra field is unused and will always point to an empty string.) Note: In PostgreSQL 6.4 and later, the be_pid is that of the notifying server process, whereas in earlier versions it was always

..............................................................................1478 E.94. Release 6.4 .................................................................................................. PGconn structure because they are subject to change in the future. (Beginning in PostgreSQL release 6.4, the definition of the struct behind PGconn is not even provided in libpq-fe.h. If you have old code present, the extra field is unused and will always point to an empty string.) Note: In PostgreSQL 6.4 and later, the be_pid is that of the notifying server process, whereas in earlier versions it was always

.............................................................................1624 E.126. Release 6.4 .................................................................................................. identifying rows is via sequences and the SERIAL type, which have been supported since PostgreSQL 6.4. • Add E” syntax so eventually ordinary strings can treat backslashes literally (Bruce) Currently additional bug fix. E.124.1. Migration to Version 6.4.2 A dump/restore is not required for those running 6.4.*. E.124.2. Changes Fix for datetime constant problem on some platforms(Thomas) 1623 Appendix E

.............................................................................1659 E.151. Release 6.4 .................................................................................................. identifying rows is via sequences and the SERIAL type, which have been supported since PostgreSQL 6.4. • Add E” syntax so eventually ordinary strings can treat backslashes literally (Bruce) Currently those running 6.4.*. E.149.2. Changes Fix for datetime constant problem on some platforms(Thomas) E.150. Release 6.4.1 Release date: 1998-12-18 This is basically a cleanup release for 6.4. We have fixed

.............................................................................1963 E.199. Release 6.4 .................................................................................................. String Comparison Behavior....................................................................1999 F.6.4. Limitations ..................................................................................... identifying rows is via sequences and the SERIAL type, which have been supported since PostgreSQL 6.4. • Add E” syntax so eventually ordinary strings can treat backslashes literally (Bruce) Currently

.............................................................................2091 E.199. Release 6.4 .................................................................................................. Comparison Behavior...........................................................................2129 F.6.4. Limitations ..................................................................................... identifying rows is via sequences and the SERIAL type, which have been supported since PostgreSQL 6.4. • Add E” syntax so eventually ordinary strings can treat backslashes literally (Bruce) Currently

.............................................................................2259 E.222. Release 6.4 .................................................................................................. Comparison Behavior...........................................................................2297 F.6.4. Limitations ..................................................................................... identifying rows is via sequences and the SERIAL type, which have been supported since PostgreSQL 6.4. • Add E” syntax so eventually ordinary strings can treat backslashes literally (Bruce) Currently

.............................................................................2120 E.222. Release 6.4 .................................................................................................. String Comparison Behavior....................................................................2156 F.6.4. Limitations ..................................................................................... identifying rows is via sequences and the SERIAL type, which have been supported since PostgreSQL 6.4. • Add E” syntax so eventually ordinary strings can treat backslashes literally (Bruce) Currently