[COMMITTERS] pgsql: I've created a patch which adds support for troff "-ms" output to
Log Message: --- I've created a patch which adds support for troff "-ms" output to psql. i.e. "\pset format troff-ms". The patch also corrects some problems with the "latex" format, notably defining an extra column in the output table, and correcting some alignment issues; it also changes the output to match the border setting as documented in the manual page and as shown with the "aligned" format. The troff-ms output is mostly identical to the latex output allowing for the differences between the two typesetters. The output should be saved in a file and piped as follows: cat file | tbl | troff -T ps -ms > file.ps or tbl file | troff -T ps -ms > file.ps Because it contains tabs, you'll need to redirect psql output or use "script", rather than pasting from a terminal window, due to the tabs which can be replaced with spaces. Roger Leigh Modified Files: -- pgsql/doc/src/sgml/ref: psql-ref.sgml (r1.138 -> r1.139) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/psql-ref.sgml.diff?r1=1.138&r2=1.139) pgsql/src/bin/psql: command.c (r1.143 -> r1.144) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/command.c.diff?r1=1.143&r2=1.144) print.c (r1.55 -> r1.56) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/print.c.diff?r1=1.55&r2=1.56) print.h (r1.22 -> r1.23) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/print.h.diff?r1=1.22&r2=1.23) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Please find attached a patch (diff -c against cvs HEAD) to add a
Log Message: --- Please find attached a patch (diff -c against cvs HEAD) to add a function that accepts a double precision argument assumed to be a Unix epoch timestamp and returns timestamp with time zone, and accompanying documentation. Usage: test=# select to_timestamp(200120400); to_timestamp 1976-05-05 14:00:00+09 (1 row) Michael Glaesemann Modified Files: -- pgsql/doc/src/sgml: func.sgml (r1.252 -> r1.253) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.252&r2=1.253) pgsql/src/include/catalog: pg_proc.h (r1.364 -> r1.365) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/pg_proc.h.diff?r1=1.364&r2=1.365) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Since I needed this feature badly, I added the -n / --schema
Log Message: --- Since I needed this feature badly, I added the -n / --schema switch to pg_restore. It restores the given schemaname only. It can be used in conjunction with the -t and other switches to make the selection very fine grained. Richard van den Bergg, CISSP Modified Files: -- pgsql/doc/src/sgml/ref: pg_restore.sgml (r1.51 -> r1.52) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_restore.sgml.diff?r1=1.51&r2=1.52) pgsql/src/bin/pg_dump: pg_backup.h (r1.34 -> r1.35) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup.h.diff?r1=1.34&r2=1.35) pg_backup_archiver.c (r1.109 -> r1.110) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_backup_archiver.c.diff?r1=1.109&r2=1.110) pg_restore.c (r1.70 -> r1.71) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/pg_dump/pg_restore.c.diff?r1=1.70&r2=1.71) ---(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: Add example for pg_config --configure.
Log Message: --- Add example for pg_config --configure. Modified Files: -- pgsql/doc/src/sgml/ref: pg_config-ref.sgml (r1.19 -> r1.20) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_config-ref.sgml.diff?r1=1.19&r2=1.20) ---(end of broadcast)--- TIP 8: explain analyze is your friend
[COMMITTERS] pgsql: Put a critical section around update of hash index metapage.
Log Message: --- Put a critical section around update of hash index metapage. Per discussion with Qingqing Zhou. Modified Files: -- pgsql/src/backend/access/hash: hashpage.c (r1.49 -> r1.50) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hashpage.c.diff?r1=1.49&r2=1.50) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: \(rs should be \\(rs, per Tom.
Log Message: --- \(rs should be \\(rs, per Tom. Modified Files: -- pgsql/src/bin/psql: print.c (r1.56 -> r1.57) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/print.c.diff?r1=1.56&r2=1.57) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: Avoid bare 'struct Node;' declaration --- provokes annoying
Log Message: --- Avoid bare 'struct Node;' declaration --- provokes annoying warnings on some compilers. Modified Files: -- pgsql/src/include: fmgr.h (r1.38 -> r1.39) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/fmgr.h.diff?r1=1.38&r2=1.39) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Repair error in description of nonblocking usage of
Log Message: --- Repair error in description of nonblocking usage of PQgetCopyData(). Per Volkan Yazici. Modified Files: -- pgsql/doc/src/sgml: libpq.sgml (r1.182 -> r1.183) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/libpq.sgml.diff?r1=1.182&r2=1.183) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Repair error in description of nonblocking usage of
Log Message: --- Repair error in description of nonblocking usage of PQgetCopyData(). Per Volkan Yazici. Tags: REL7_4_STABLE Modified Files: -- pgsql/doc/src/sgml: libpq.sgml (r1.141.2.1 -> r1.141.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/libpq.sgml.diff?r1=1.141.2.1&r2=1.141.2.2) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Repair error in description of nonblocking usage of
Log Message: --- Repair error in description of nonblocking usage of PQgetCopyData(). Per Volkan Yazici. Tags: REL8_0_STABLE Modified Files: -- pgsql/doc/src/sgml: libpq.sgml (r1.178.4.1 -> r1.178.4.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/libpq.sgml.diff?r1=1.178.4.1&r2=1.178.4.2) ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Defend against omitted paramLengths[] array in PQsendQueryParams.
Log Message: --- Defend against omitted paramLengths[] array in PQsendQueryParams. Per Volkan Yazici. Modified Files: -- pgsql/src/interfaces/libpq: fe-exec.c (r1.167 -> r1.168) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-exec.c.diff?r1=1.167&r2=1.168) libpq-fe.h (r1.116 -> r1.117) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/libpq-fe.h.diff?r1=1.116&r2=1.117) ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Add missing #include -- mea culpa.
Log Message: --- Add missing #include -- mea culpa. Modified Files: -- pgsql/src/backend/access/hash: hashpage.c (r1.50 -> r1.51) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hashpage.c.diff?r1=1.50&r2=1.51) ---(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: Make SPI set SPI_processed for CREATE TABLE AS / SELECT INTO
Log Message: --- Make SPI set SPI_processed for CREATE TABLE AS / SELECT INTO commands; this in turn causes CREATE TABLE AS in plpgsql to set ROW_COUNT. This is how it behaved before 7.4; I had unintentionally changed the behavior in a bit of sloppy micro-optimization. Modified Files: -- pgsql/src/backend/executor: spi.c (r1.140 -> r1.141) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/executor/spi.c.diff?r1=1.140&r2=1.141) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Fix assign_datestyle() so that it doesn't misleadingly complain
Log Message: --- Fix assign_datestyle() so that it doesn't misleadingly complain about 'conflicting datestyle specifications' for input that's actually only redundant, such as SET DATESTYLE = MDY, MDY. Per recent gripe. Modified Files: -- pgsql/src/backend/commands: variable.c (r1.107 -> r1.108) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/variable.c.diff?r1=1.107&r2=1.108) ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[COMMITTERS] pgsql: Fix typo in comment, per Alvaro.
Log Message: --- Fix typo in comment, per Alvaro. Modified Files: -- pgsql/src/backend/postmaster: postmaster.c (r1.451 -> r1.452) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c.diff?r1=1.451&r2=1.452) ---(end of broadcast)--- TIP 8: explain analyze is your friend
[COMMITTERS] pgsql: This patch against 8.0.0beta1 source adds log_line_prefix options
Log Message: --- This patch against 8.0.0beta1 source adds log_line_prefix options for millisecond timestamps (%m) and remote host (%h). The milliseconds are useful for QPS measurements. Ed L. Modified Files: -- pgsql/doc/src/sgml: runtime.sgml (r1.322 -> r1.323) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/runtime.sgml.diff?r1=1.322&r2=1.323) pgsql/src/backend/utils/error: elog.c (r1.158 -> r1.159) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/error/elog.c.diff?r1=1.158&r2=1.159) pgsql/src/backend/utils/misc: postgresql.conf.sample (r1.143 -> r1.144) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/postgresql.conf.sample.diff?r1=1.143&r2=1.144) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Free buffer allocated via malloc (process is short-lived, but fix
Log Message: --- Free buffer allocated via malloc (process is short-lived, but fix it anyway). Modified Files: -- pgsql/src/backend/access/transam: xlog.c (r1.198 -> r1.199) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c.diff?r1=1.198&r2=1.199) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
[COMMITTERS] pgsql: Restructure log_line_prefix options to be clearer:
Log Message: --- Restructure log_line_prefix options to be clearer: #log_line_prefix = '' # %u = user name # %d = database name # %r = remote host and port # %h = remote host # %p = PID # %t = timestamp # %m = timestamp with milliseconds # %i = command tag # %c = session id # %l = session line number # %s = session start timestamp # %x = transaction id # %q = stop here in non-session processes # %% = '%' # e.g. '<%u%%%d> ' Modified Files: -- pgsql/src/backend/utils/misc: postgresql.conf.sample (r1.144 -> r1.145) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/postgresql.conf.sample.diff?r1=1.144&r2=1.145) ---(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: Mention prefix %t has no milliseconds.
Log Message: --- Mention prefix %t has no milliseconds. Modified Files: -- pgsql/doc/src/sgml: runtime.sgml (r1.323 -> r1.324) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/runtime.sgml.diff?r1=1.323&r2=1.324) pgsql/src/backend/utils/misc: postgresql.conf.sample (r1.145 -> r1.146) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/postgresql.conf.sample.diff?r1=1.145&r2=1.146) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: This patch shows the full path name when doing a \s in psql, if
Log Message: --- This patch shows the full path name when doing a \s in psql, if you have previously issued a \cd command. Greg Sabino Mullane Modified Files: -- pgsql/src/bin/psql: command.c (r1.144 -> r1.145) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/command.c.diff?r1=1.144&r2=1.145) settings.h (r1.23 -> r1.24) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/settings.h.diff?r1=1.23&r2=1.24) ---(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: Revise searching of subplan target lists to use something more
Log Message: --- Revise searching of subplan target lists to use something more efficient than tlist_member calls. Building a large join tlist is still O(N^2), but with a much smaller constant factor than before. Modified Files: -- pgsql/src/backend/optimizer/plan: setrefs.c (r1.110 -> r1.111) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/setrefs.c.diff?r1=1.110&r2=1.111) ---(end of broadcast)--- TIP 8: explain analyze is your friend
[COMMITTERS] pgsql: If a LIMIT is applied to a UNION ALL query, plan each UNION arm
Log Message: --- If a LIMIT is applied to a UNION ALL query, plan each UNION arm as if the limit were directly applied to it. This does not actually add a LIMIT plan node to the generated subqueries --- that would be useless overhead --- but it does cause the planner to prefer fast- start plans when the limit is small. After an idea from Phil Endecott. Modified Files: -- pgsql/src/backend/optimizer/plan: planner.c (r1.188 -> r1.189) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/planner.c.diff?r1=1.188&r2=1.189) pgsql/src/backend/optimizer/prep: prepunion.c (r1.123 -> r1.124) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/prep/prepunion.c.diff?r1=1.123&r2=1.124) pgsql/src/include/optimizer: prep.h (r1.50 -> r1.51) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/optimizer/prep.h.diff?r1=1.50&r2=1.51) ---(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: Add the "PGPASSFILE" environment variable to specify to the
Log Message: --- Add the "PGPASSFILE" environment variable to specify to the password file. Andrew Dunstan Modified Files: -- pgsql/doc/src/sgml: libpq.sgml (r1.183 -> r1.184) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/libpq.sgml.diff?r1=1.183&r2=1.184) pgsql/src/interfaces/libpq: fe-connect.c (r1.307 -> r1.308) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-connect.c.diff?r1=1.307&r2=1.308) ---(end of broadcast)--- TIP 8: explain analyze is your friend
[COMMITTERS] pgsql: Quick hack to allow the outer query's tuple_fraction to be passed
Log Message: --- Quick hack to allow the outer query's tuple_fraction to be passed down to a subquery if the outer query is simple enough that the LIMIT can be reflected directly to the subquery. This didn't use to be very interesting, because a subquery that couldn't have been flattened into the upper query was usually not going to be very responsive to tuple_fraction anyway. But with new code that allows UNION ALL subqueries to pay attention to tuple_fraction, this is useful to do. In particular this lets the optimization occur when the UNION ALL is directly inside a view. Modified Files: -- pgsql/src/backend/optimizer/path: allpaths.c (r1.133 -> r1.134) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/path/allpaths.c.diff?r1=1.133&r2=1.134) pgsql/src/backend/optimizer/plan: planmain.c (r1.84 -> r1.85) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/optimizer/plan/planmain.c.diff?r1=1.84&r2=1.85) pgsql/src/include/nodes: relation.h (r1.113 -> r1.114) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/nodes/relation.h.diff?r1=1.113&r2=1.114) ---(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: Remove unneeded variable test, per Tom.
Log Message: --- Remove unneeded variable test, per Tom. Modified Files: -- pgsql/src/interfaces/libpq: fe-connect.c (r1.308 -> r1.309) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-connect.c.diff?r1=1.308&r2=1.309) ---(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
