[COMMITTERS] pgsql-server/ oc/src/sgml/Tag: oc/src/sgml/REL ...

2003-11-30 Thread Joe Conway
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED]   03/11/30 16:52:37

Modified files:
doc/src/sgml   : Tag: REL7_3_STABLE datatype.sgml 
src/backend/utils/adt: Tag: REL7_3_STABLE varlena.c 
src/interfaces/libpq: Tag: REL7_3_STABLE fe-exec.c 

Log message:
Make PQescapeBytea and byteaout consistent with each other, and
octal escape all octets outside the range 0x20 to 0x7e. This fixes
the problem pointed out by Sergey Yatskevich here:
http://archives.postgresql.org/pgsql-bugs/2003-11/msg00140.php


---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org


[COMMITTERS] pgsql-server/ oc/src/sgml/Tag: oc/src/sgml/REL ...

2003-11-30 Thread Joe Conway
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED]   03/11/30 16:53:43

Modified files:
doc/src/sgml   : Tag: REL7_4_STABLE datatype.sgml 
src/backend/utils/adt: Tag: REL7_4_STABLE varlena.c 
src/interfaces/libpq: Tag: REL7_4_STABLE fe-exec.c 

Log message:
Make PQescapeBytea and byteaout consistent with each other, and
octal escape all octets outside the range 0x20 to 0x7e. This fixes
the problem pointed out by Sergey Yatskevich here:
http://archives.postgresql.org/pgsql-bugs/2003-11/msg00140.php


---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match


[COMMITTERS] pgsql-server/ oc/src/sgml/datatype.sgml rc/bac ...

2003-11-30 Thread Joe Conway
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED]   03/11/30 16:55:09

Modified files:
doc/src/sgml   : datatype.sgml 
src/backend/utils/adt: varlena.c 
src/interfaces/libpq: fe-exec.c 

Log message:
Make PQescapeBytea and byteaout consistent with each other, and
octal escape all octets outside the range 0x20 to 0x7e. This fixes
the problem pointed out by Sergey Yatskevich here:
http://archives.postgresql.org/pgsql-bugs/2003-11/msg00140.php


---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings


[COMMITTERS] pgsql-server/src backend/port/Tag: backend/por ...

2003-11-30 Thread Tom Lane
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED]   03/11/30 17:56:36

Modified files:
src/backend/port: Tag: REL7_3_STABLE sysv_shmem.c 
src/backend/postmaster: Tag: REL7_3_STABLE pgstat.c 
src/include/storage: Tag: REL7_3_STABLE pg_shmem.h 

Log message:
Back-patch fix to cause stats processes to detach from shared memory,
so that they do not prevent the postmaster from deleting the shmem segment
during crash recovery.


---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match


[COMMITTERS] pgsql-server/src/backend/optimizer/plan Tag: R ...

2003-11-30 Thread Tom Lane
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED]   03/11/30 18:24:17

Modified files:
src/backend/optimizer/plan: Tag: REL7_3_STABLE subselect.c 

Log message:
Back-patch fix to check vartypmod when matching PlannerParamVar entries.
This should prevent some obscure cases of 'variable not in subplan target
lists', although actual failures have only been reported against 7.4 in
which the bug is much easier to trigger.


---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match


[COMMITTERS] CVSROOT/. options

2003-11-30 Thread PostgreSQL Daemon
CVSROOT:/cvsroot
Module name:CVSROOT
Changes by: [EMAIL PROTECTED]   03/11/30 19:40:48

Modified files:
.  : options 

Log message:
disable disabling Header/Id


---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster


[COMMITTERS] pgsql-server/src/backend/utils/misc guc.c

2003-11-30 Thread Bruce Momjian
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED]   03/11/30 23:55:22

Modified files:
src/backend/utils/misc: guc.c 

Log message:
Seems there are three GUC variables that are defined as "Shows ..."
while you can actually set them with SET.

This applied patch changes the wording from "Show" to "Set".


---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faqs/FAQ.html