[COMMITTERS] press - pr: Remove completely broken link that somehow confused the
Log Message: --- Remove completely broken link that somehow confused the mirrorer. Can't beleiev we didn't see this one before :) Modified Files: -- pr/releases/8.1/el: presskit81.html.el (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/press/pr/releases/8.1/el/presskit81.html.el.diff?r1=1.4&r2=1.5) ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings
[COMMITTERS] pgfouine - pgfouine: abitily to write several lines at once
Log Message: --- abitily to write several lines at once Modified Files: -- pgfouine/include/reporting/artichow/php4/inc: Font.class.php (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/reporting/artichow/php4/inc/Font.class.php.diff?r1=1.1&r2=1.2) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgfouine - pgfouine: more work on graphs
Log Message: --- more work on graphs Modified Files: -- pgfouine/include/reporting/reports: HourlyStatsReport.class.php (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/include/reporting/reports/HourlyStatsReport.class.php.diff?r1=1.2&r2=1.3) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgfouine - pgfouine: updated ChangeLog
Log Message: --- updated ChangeLog Modified Files: -- pgfouine: ChangeLog (r1.8 -> r1.9) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/ChangeLog.diff?r1=1.8&r2=1.9) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Update interval documenation to mention the storage system used.
Log Message: --- Update interval documenation to mention the storage system used. Modified Files: -- pgsql/doc/src/sgml: datatype.sgml (r1.163 -> r1.164) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/datatype.sgml.diff?r1=1.163&r2=1.164) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Update interval documenation to mention the storage system used.
Log Message: --- Update interval documenation to mention the storage system used. Tags: REL8_1_STABLE Modified Files: -- pgsql/doc/src/sgml: datatype.sgml (r1.163 -> r1.163.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/datatype.sgml.diff?r1=1.163&r2=1.163.2.1) ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
[COMMITTERS] pgsql: Adjust string comparison so that only bitwise-equal strings are
Log Message: --- Adjust string comparison so that only bitwise-equal strings are considered equal: if strcoll claims two strings are equal, check it with strcmp, and sort according to strcmp if not identical. This fixes inconsistent behavior under glibc's hu_HU locale, and probably under some other locales as well. Also, take advantage of the now-well-defined behavior to speed up texteq, textne, bpchareq, bpcharne: they may as well just do a bitwise comparison and not bother with strcoll at all. NOTE: affected databases may need to REINDEX indexes on text columns to be sure they are self-consistent. Modified Files: -- pgsql/src/backend/access/hash: hashfunc.c (r1.45 -> r1.46) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hashfunc.c.diff?r1=1.45&r2=1.46) pgsql/src/backend/utils/adt: varchar.c (r1.113 -> r1.114) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/varchar.c.diff?r1=1.113&r2=1.114) varlena.c (r1.141 -> r1.142) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/varlena.c.diff?r1=1.141&r2=1.142) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Adjust string comparison so that only bitwise-equal strings are
Log Message: --- Adjust string comparison so that only bitwise-equal strings are considered equal: if strcoll claims two strings are equal, check it with strcmp, and sort according to strcmp if not identical. This fixes inconsistent behavior under glibc's hu_HU locale, and probably under some other locales as well. Also, take advantage of the now-well-defined behavior to speed up texteq, textne, bpchareq, bpcharne: they may as well just do a bitwise comparison and not bother with strcoll at all. NOTE: affected databases may need to REINDEX indexes on text columns to be sure they are self-consistent. Tags: REL8_1_STABLE Modified Files: -- pgsql/src/backend/access/hash: hashfunc.c (r1.45 -> r1.45.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/hash/hashfunc.c.diff?r1=1.45&r2=1.45.2.1) pgsql/src/backend/utils/adt: varchar.c (r1.113 -> r1.113.2.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/varchar.c.diff?r1=1.113&r2=1.113.2.1) varlena.c (r1.139.2.1 -> r1.139.2.2) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/varlena.c.diff?r1=1.139.2.1&r2=1.139.2.2) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Adjust string comparison so that only bitwise-equal strings are
Log Message: --- Adjust string comparison so that only bitwise-equal strings are considered equal: if strcoll claims two strings are equal, check it with strcmp, and sort according to strcmp if not identical. This fixes inconsistent behavior under glibc's hu_HU locale, and probably under some other locales as well. Also, take advantage of the now-well-defined behavior to speed up texteq, textne, bpchareq, bpcharne: they may as well just do a bitwise comparison and not bother with strcoll at all. NOTE: affected databases may need to REINDEX indexes on text columns to be sure they are self-consistent. Tags: REL8_0_STABLE Modified Files: -- pgsql/src/backend/utils/adt: varchar.c (r1.108 -> r1.108.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/varchar.c.diff?r1=1.108&r2=1.108.4.1) varlena.c (r1.118 -> r1.118.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/varlena.c.diff?r1=1.118&r2=1.118.4.1) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] pgsql: Adjust string comparison so that only bitwise-equal strings are
Log Message: --- Adjust string comparison so that only bitwise-equal strings are considered equal: if strcoll claims two strings are equal, check it with strcmp, and sort according to strcmp if not identical. This fixes inconsistent behavior under glibc's hu_HU locale, and probably under some other locales as well. Also, take advantage of the now-well-defined behavior to speed up texteq, textne, bpchareq, bpcharne: they may as well just do a bitwise comparison and not bother with strcoll at all. NOTE: affected databases may need to REINDEX indexes on text columns to be sure they are self-consistent. Tags: REL7_4_STABLE Modified Files: -- pgsql/src/backend/utils/adt: varchar.c (r1.102 -> r1.102.4.1) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/varchar.c.diff?r1=1.102&r2=1.102.4.1) varlena.c (r1.106.2.4 -> r1.106.2.5) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/varlena.c.diff?r1=1.106.2.4&r2=1.106.2.5) ---(end of broadcast)--- TIP 1: 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: Adjust string comparison so that only bitwise-equal strings are
Log Message: --- Adjust string comparison so that only bitwise-equal strings are considered equal: if strcoll claims two strings are equal, check it with strcmp, and sort according to strcmp if not identical. This fixes inconsistent behavior under glibc's hu_HU locale, and probably under some other locales as well. Also, take advantage of the now-well-defined behavior to speed up texteq, textne, bpchareq, bpcharne: they may as well just do a bitwise comparison and not bother with strcoll at all. NOTE: affected databases may need to REINDEX indexes on text columns to be sure they are self-consistent. Tags: REL7_3_STABLE Modified Files: -- pgsql/src/backend/utils/adt: varlena.c (r1.92.2.3 -> r1.92.2.4) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/varlena.c.diff?r1=1.92.2.3&r2=1.92.2.4) ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
[COMMITTERS] pgsql: Update item: > > A more complex solution would be to save
Log Message: --- Update item: > > A more complex solution would be to save multiple plans for different > cardinality and use the appropriate plan based on the EXECUTE values. > Modified Files: -- pgsql/doc: TODO (r1.1734 -> r1.1735) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1734&r2=1.1735) pgsql/doc/src/FAQ: TODO.html (r1.239 -> r1.240) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html.diff?r1=1.239&r2=1.240) ---(end of broadcast)--- TIP 1: 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 quotes around search_path "$user" so that SHOW output can be
Log Message: --- Add quotes around search_path "$user" so that SHOW output can be used in SET. Modified Files: -- pgsql/doc/src/sgml: config.sgml (r1.39 -> r1.40) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/config.sgml.diff?r1=1.39&r2=1.40) ddl.sgml (r1.50 -> r1.51) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ddl.sgml.diff?r1=1.50&r2=1.51) pgsql/src/backend/utils/misc: guc.c (r1.302 -> r1.303) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/guc.c.diff?r1=1.302&r2=1.303) postgresql.conf.sample (r1.171 -> r1.172) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/misc/postgresql.conf.sample.diff?r1=1.171&r2=1.172) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
[COMMITTERS] pgsql: Add an officially exported libpq function to encrypt passwords,
Log Message: --- Add an officially exported libpq function to encrypt passwords, and modify the previous \password patch to use it instead of depending on a not-officially-exported function. Per discussion. Modified Files: -- pgsql/doc/src/sgml: libpq.sgml (r1.199 -> r1.200) (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/libpq.sgml.diff?r1=1.199&r2=1.200) pgsql/src/bin/psql: command.c (r1.156 -> r1.157) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/command.c.diff?r1=1.156&r2=1.157) pgsql/src/bin/scripts: createuser.c (r1.24 -> r1.25) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/scripts/createuser.c.diff?r1=1.24&r2=1.25) pgsql/src/interfaces/libpq: exports.txt (r1.5 -> r1.6) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/exports.txt.diff?r1=1.5&r2=1.6) fe-auth.c (r1.108 -> r1.109) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-auth.c.diff?r1=1.108&r2=1.109) libpq-fe.h (r1.122 -> r1.123) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/libpq-fe.h.diff?r1=1.122&r2=1.123) ---(end of broadcast)--- TIP 6: explain analyze is your friend
[COMMITTERS] pgsql: Fix for rearranging encoding id ISO-8859-5 to ISO-8859-8.
Log Message: --- Fix for rearranging encoding id ISO-8859-5 to ISO-8859-8. Also make the code more robust by searching for target encoding in the internal charset map. Problem reported by Sagi Bashari on 2005/12/21. See "[BUGS] BUG #2120: Crash when doing UTF8<->ISO_8859_8 encoding conversion" on pgsql-bugs list for more details. Modified Files: -- pgsql/src/backend/utils/mb/conversion_procs/utf8_and_iso8859: utf8_and_iso8859.c (r1.16 -> r1.17) (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mb/conversion_procs/utf8_and_iso8859/utf8_and_iso8859.c.diff?r1=1.16&r2=1.17) ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[COMMITTERS] wikipedia - wikipgedia: additional check before eval
Log Message: --- additional check before eval Modified Files: -- wikipgedia/includes: Setup.php (r1.2 -> r1.3) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/wikipedia/wikipgedia/includes/Setup.php.diff?r1=1.2&r2=1.3) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [COMMITTERS] pgsql: Fix for rearranging encoding id ISO-8859-5
Tatsuo Ishii wrote: Fix for rearranging encoding id ISO-8859-5 to ISO-8859-8. Also make the code more robust by searching for target encoding in the internal charset map. ISTM this patch, or some variant of it, should be applied to the REL8_1_STABLE branch, and any earlier release branches that also exhibit the problem. -Neil ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [COMMITTERS] pgsql: Fix for rearranging encoding id ISO-8859-5
Neil Conway <[EMAIL PROTECTED]> writes: > Tatsuo Ishii wrote: >> Fix for rearranging encoding id ISO-8859-5 to ISO-8859-8. >> Also make the code more robust by searching for target encoding >> in the internal charset map. > ISTM this patch, or some variant of it, should be applied to the > REL8_1_STABLE branch, and any earlier release branches that also exhibit > the problem. 8.1 definitely needs to be fixed. I don't think there is a bug in 8.0, though that should be double-checked. regards, tom lane ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [COMMITTERS] pgsql: Fix for rearranging encoding id ISO-8859-5
Tom Lane wrote: > Neil Conway <[EMAIL PROTECTED]> writes: > > Tatsuo Ishii wrote: > >> Fix for rearranging encoding id ISO-8859-5 to ISO-8859-8. > >> Also make the code more robust by searching for target encoding > >> in the internal charset map. > > > ISTM this patch, or some variant of it, should be applied to the > > REL8_1_STABLE branch, and any earlier release branches that also exhibit > > the problem. > > 8.1 definitely needs to be fixed. I don't think there is a bug in 8.0, > though that should be double-checked. 8.0.X looked OK to me. -- Bruce Momjian| http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
