Andrew Dunstan <[EMAIL PROTECTED]> writes:
> can you the missing space on the marked line, or do you need another
> patch from me?
Fixed.
regards, tom lane
---(end of broadcast)---
TIP 8: explain analyze is your friend
Bruce,
can you the missing space on the marked line, or do you need another
patch from me?
thanks
andrew
Andriy Tkachuk wrote:
seems to be little syntax problem:
On Thu, 4 Sep 2003, Bruce Momjian wrote:
Patch applied. Thanks.
seems to be little syntax problem:
On Thu, 4 Sep 2003, Bruce Momjian wrote:
>
> Patch applied. Thanks.
>
> ---
>
>
> Andrew Dunstan wrote:
...
> >
> > !
> > ! To avoid this situation, run PostgreSQL
> > ! on a ma
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
It's highly unsatisfactory, but it's a fact nonetheless. The stock
kernel simply checks for a non-zero value in this variable and says "OK,
give them the memory" if it finds it. So if you are using such a kernel,
then setting the non-zero value turns off all checking, rather than
using the defa
Andrew Dunstan writes:
> +
> + 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
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 tag in the doc sources.
I did find a warning in an unadorned para, in func.sgml.
Anyway, I made the changes (using ) but ano
I didn't find a single instance of a tag in the doc sources. I
did find a warning in an unadorned para, in func.sgml.
Anyway, I made the changes (using ) 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 only concern
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 "PostgreSQL".
> ! altering the system's default behaviour. This can be determined
> ! by examining the function
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
10 matches
Mail list logo
