Log Message:
---
Update 9.0 release notes so streaming replication and hot standby is not
assumed to require continuous archiving.
Per report from Fujii Masao
Modified Files:
--
pgsql/doc/src/sgml:
release-9.0.sgml (r2.37 -> r2.38)
(http://anoncvs.postgres
Log Message:
---
stringToNode() and deparse_expression_pretty() crash on invalid input,
but we have nevertheless exposed them to users via pg_get_expr(). It would
be too much maintenance effort to rigorously check the input, so put a hack
in place instead to restrict pg_get_expr() so that t
Log Message:
---
stringToNode() and deparse_expression_pretty() crash on invalid input,
but we have nevertheless exposed them to users via pg_get_expr(). It would
be too much maintenance effort to rigorously check the input, so put a hack
in place instead to restrict pg_get_expr() so that t
Log Message:
---
stringToNode() and deparse_expression_pretty() crash on invalid input,
but we have nevertheless exposed them to users via pg_get_expr(). It would
be too much maintenance effort to rigorously check the input, so put a hack
in place instead to restrict pg_get_expr() so that t
Log Message:
---
stringToNode() and deparse_expression_pretty() crash on invalid input,
but we have nevertheless exposed them to users via pg_get_expr(). It would
be too much maintenance effort to rigorously check the input, so put a hack
in place instead to restrict pg_get_expr() so that t
Log Message:
---
stringToNode() and deparse_expression_pretty() crash on invalid input,
but we have nevertheless exposed them to users via pg_get_expr(). It would
be too much maintenance effort to rigorously check the input, so put a hack
in place instead to restrict pg_get_expr() so that t
Log Message:
---
stringToNode() and deparse_expression_pretty() crash on invalid input,
but we have nevertheless exposed them to users via pg_get_expr(). It would
be too much maintenance effort to rigorously check the input, so put a hack
in place instead to restrict pg_get_expr() so that t
Log Message:
---
stringToNode() and deparse_expression_pretty() crash on invalid input,
but we have nevertheless exposed them to users via pg_get_expr(). It would
be too much maintenance effort to rigorously check the input, so put a hack
in place instead to restrict pg_get_expr() so that t
Log Message:
---
Correct missing/misspelled surname.
Modified Files:
--
pgsql/doc/src/sgml:
release-9.0.sgml (r2.36 -> r2.37)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release-9.0.sgml?r1=2.36&r2=2.37)
--
Sent via pgsql-committers maili
Log Message:
---
"echo" had nothing to do there...
Modified Files:
--
slony-ctl/outils:
slony_repstat.sh (r1.7 -> r1.8)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/slony1-ctl/slony-ctl/outils/slony_repstat.sh?r1=1.7&r2=1.8)
--
Sent via pgsql-committers m
10 matches
Mail list logo
