[COMMITTERS] pgsql-server/src backend/catalog/information_s ...
CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/02/03 04:29:57 Modified files: src/backend/catalog: information_schema.sql src/backend/utils/adt: int.c int8.c src/include/catalog: catversion.h pg_proc.h src/include/utils: builtins.h int8.h Log message: Add function (actually an int4 and an int8 version) that generates a series of numbers, optionally using an explicit step size other than the default value (one). Use function in the information_schema to replace hard-wired knowledge of INDEX_MAX_KEYS. initdb forced due to pg_proc change. Documentation update still needed -- will be committed separately. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[COMMITTERS] pgsql-server/doc TODO
CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/02/03 12:53:56 Modified files: doc: TODO Log message: Add: * Make pg_restore continue after errors, so it acts more like pg_dump scripts ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql-server/ ontrib/tablefunc/tablefunc.c oc/ ...
CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/02/03 13:34:04 Modified files: contrib/tablefunc: tablefunc.c doc/src/sgml : backup.sgml installation.sgml perform.sgml plpgsql.sgml runtime.sgml doc/src/sgml/ref: postgres-ref.sgml postmaster.sgml src/backend/access/nbtree: nbtree.c nbtsort.c src/backend/commands: vacuumlazy.c src/backend/executor: execQual.c nodeAgg.c nodeHash.c nodeIndexscan.c nodeMaterial.c nodeSort.c src/backend/optimizer/path: costsize.c src/backend/optimizer/plan: planner.c subselect.c src/backend/optimizer/util: pathnode.c src/backend/tcop: postgres.c src/backend/utils/adt: ri_triggers.c src/backend/utils/init: globals.c src/backend/utils/misc: guc.c postgresql.conf.sample src/backend/utils/mmgr: portalmem.c src/backend/utils/sort: tuplesort.c tuplestore.c src/bin/psql : tab-complete.c src/include/access: nbtree.h src/include: miscadmin.h src/include/utils: tuplesort.h src/pl/plpgsql/src: pl_exec.c Log message: Rename SortMem and VacuumMem to work_mem and maintenance_work_mem. Make btree index creation and initial validation of foreign-key constraints use maintenance_work_mem rather than work_mem as their memory limit. Add some code to guc.c to allow these variables to be referenced by their old names in SHOW and SET commands, for backwards compatibility. ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql-server/src/backend/utils/adt regexp.c
CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/02/03 13:52:55 Modified files: src/backend/utils/adt: regexp.c Log message: pwd ---(end of broadcast)--- TIP 8: explain analyze is your friend
[COMMITTERS] pgsql-server/src/backend/utils/adt Tag: REL7_4 ...
CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/02/03 13:56:04 Modified files: src/backend/utils/adt: Tag: REL7_4_STABLE regexp.c Log message: Ensure that memcmp() does not run off the end of memory, per Kurt Roeckx. (Same patch committed to HEAD but I fat-fingered the commit message...) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql-server/src/interfaces/jdbc/org/postgresq ...
CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/02/03 01:00:21 Modified files: src/interfaces/jdbc/org/postgresql/jdbc2/optional: Tag: REL7_4_STABLE PooledConnectionImpl.java Log message: Newer versions of the 1.4.2 jdk give warnings about having return in a finally clause. ---(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/interfaces/jdbc/org/postgresq ...
CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/02/03 01:43:26 Modified files: src/interfaces/jdbc/org/postgresql/core: Tag: REL7_4_STABLE QueryExecutor.java src/interfaces/jdbc/org/postgresql/fastpath: Tag: REL7_4_STABLE Fastpath.java src/interfaces/jdbc/org/postgresql/test/jdbc2: Tag: REL7_4_STABLE Jdbc2TestSuite.java Added files: src/interfaces/jdbc/org/postgresql/test/jdbc2: Tag: REL7_4_STABLE NotifyTest.java Log message: V3 NotificationResonse messages were trying to be received as V2 messages. Also the PID was being read in the wrong byte order. Finally add a test case for listen/notify. Per report from Hans Nather. ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[COMMITTERS] pgsql-server/src/interfaces/jdbc/org/postgresq ...
CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/02/03 01:25:39 Modified files: src/interfaces/jdbc/org/postgresql/jdbc1: Tag: REL7_4_STABLE AbstractJdbc1ResultSet.java src/interfaces/jdbc/org/postgresql/jdbc2: Tag: REL7_4_STABLE AbstractJdbc2ResultSet.java src/interfaces/jdbc/org/postgresql/test/jdbc2: Tag: REL7_4_STABLE ResultSetTest.java Log message: ResultSet.next() and previous() incremented or decremented the internal current_row variable regardless of wether they succeeded or not. This generated some ArrayIndexOutOfBoundsExceptions when the errorneous adjustment current_row led to out of range values. Per report from Fischer Krisztian. ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
[COMMITTERS] pgsql-server/src/interfaces/jdbc/org/postgresq ...
CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/02/03 01:13:56 Modified files: src/interfaces/jdbc/org/postgresql/jdbc1: Tag: REL7_4_STABLE AbstractJdbc1Statement.java src/interfaces/jdbc/org/postgresql/test/jdbc2: Tag: REL7_4_STABLE Jdbc2TestSuite.java Added files: src/interfaces/jdbc/org/postgresql/test/jdbc2: Tag: REL7_4_STABLE PreparedStatementTest.java Log message: Fix the setXXXStream methods. If passed a null InputStream, convert this to a setNull call. The code originally would try to read the whole stream in one call to read(), but this doesn't work. The InputStream API makes it clear you must be prepared to loop and continue reading if you didn't get the whole request on the first try. Per report from Martin Holz. ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql-server/src/backend/utils/adt numeric.c
CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/02/03 21:11:47 Modified files: src/backend/utils/adt: numeric.c Log message: Use memmove() rather than memcpy() in set_var_from_var(). If this function is asked to assign a variable to itself, it will result in doing a memcpy() on an entirely-overlapping memory range, which results in undefined behavior according to ANSI C. That said, it is unlikely to actually do anything bad on any sane libc, but this keeps valgrind quiet. ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
[COMMITTERS] pgsql-server/src backend/storage/buffer/bufmgr ...
CVSROOT:/cvsroot Module name:pgsql-server Changes by: [EMAIL PROTECTED] 04/02/03 21:24:54 Modified files: src/backend/storage/buffer: bufmgr.c src/backend/utils/misc: guc.c postgresql.conf.sample src/include/storage: bufmgr.h Log message: Backing out the background writer sync() option. Jan ---(end of broadcast)--- TIP 8: explain analyze is your friend
Re: [COMMITTERS] pgsql-server/ ontrib/tablefunc/tablefunc.c oc/ ...
Log message: Rename SortMem and VacuumMem to work_mem and maintenance_work_mem. Make btree index creation and initial validation of foreign-key constraints use maintenance_work_mem rather than work_mem as their memory limit. Add some code to guc.c to allow these variables to be referenced by their old names in SHOW and SET commands, for backwards compatibility. Does this mean that if you go ALTER USER/SET sort_mem TO xxx, it will set the variable work_mem=xxx in their pg_shadow row? Chris ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [COMMITTERS] pgsql-server/ ontrib/tablefunc/tablefunc.c oc/ ...
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Add some code to guc.c to allow these variables to be referenced by their
old names in SHOW and SET commands, for backwards compatibility.
Does this mean that if you go ALTER USER/SET sort_mem TO xxx, it will
set the variable work_mem=xxx in their pg_shadow row?
My first answer was no, the pg_shadow row will still mention sort_mem,
but that will be accepted as meaning work_mem later on when you log in
as that user.
However, looking more closely, AlterUserSet converts option names to
canonical spelling before storing them, which means it Just Works:
regression=# create user foo;
CREATE USER
regression=# alter user foo set sort_mem = 999;
ALTER USER
regression=# select * from pg_shadow where usename = 'foo';
usename | usesysid | usecreatedb | usesuper | usecatupd | passwd | valuntil |
useconfig
-+--+-+--+---++--+
foo | 100 | f | f| f || |
{work_mem=999}
(1 row)
Dang, sometimes nice things actually fall out of the code ...
regards, tom lane
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
