seems to be little syntax problem:
On Thu, 4 Sep 2003, Bruce Momjian wrote:
Patch applied. Thanks.
---
Andrew Dunstan wrote:
...
!para
! To avoid this situation, run productnamePostgreSQL/productname
Patch applied. Thanks.
---
Andrew Dunstan wrote:
It appears we are back in the you need a non-empty password mode.
Anyway, here's the revised patch.
andrew
Andrew Dunstan wrote:
I didn't find a single
As discussed on Hackers.
enjoy
andrew
Index: doc/src/sgml/runtime.sgml
===
RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/runtime.sgml,v
retrieving revision 1.200
diff -c -w -r1.200 runtime.sgml
*** doc/src/sgml/runtime.sgml
Minor SGML gripes...
On Fri, Aug 22, 2003 at 10:00:00AM -0400, Andrew Dunstan wrote:
! To avoid this situation, run postgres on a machine where you
postgres should be productnamePostgreSQL/productname.
! altering the system's default behaviour. This can be determined
! by
I didn't find a single instance of a warning tag in the doc sources. I
did find a warning in an unadorned para, in func.sgml.
Anyway, I made the changes (using note) but anoncvs is now refusing my
login attempt, so I can't do the diff.
I've spent way too much time on this already - really my
It appears we are back in the you need a non-empty password mode.
Anyway, here's the revised patch.
andrew
Andrew Dunstan wrote:
I didn't find a single instance of a warning tag in the doc sources.
I did find a warning in an unadorned para, in func.sgml.
Anyway, I made the changes (using
Andrew Dunstan writes:
+para
+ Warning: using these settings in a kernel which does not support
+ these modes will almost certainly increase the danger of the
+ kernel killing the postmaster, rather than reducing it.
+ If in any doubt, consult a kernel expert
