<feed xmlns='http://www.w3.org/2005/Atom'>
<title>delta/postgresql.git, branch REL7_4_14</title>
<subtitle>git.postgresql.org: git/postgresql.git
</subtitle>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/postgresql.git/'/>
<entry>
<title>Stamp 7.4.14.</title>
<updated>2006-10-12T19:42:03+00:00</updated>
<author>
<name>Tom Lane</name>
<email>tgl@sss.pgh.pa.us</email>
</author>
<published>2006-10-12T19:42:03+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/postgresql.git/commit/?id=62f9cbf4241732c36e75372932ddcbd8eb01e726'/>
<id>62f9cbf4241732c36e75372932ddcbd8eb01e726</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>A bit of copy-editing on back-branch release notes.</title>
<updated>2006-10-11T20:56:21+00:00</updated>
<author>
<name>Tom Lane</name>
<email>tgl@sss.pgh.pa.us</email>
</author>
<published>2006-10-11T20:56:21+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/postgresql.git/commit/?id=1d5ad22c325f01675fab36d89ebb1e466f357a3b'/>
<id>1d5ad22c325f01675fab36d89ebb1e466f357a3b</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Repair incorrect check for coercion of unknown literal to ANYARRAY, a bug</title>
<updated>2006-10-11T20:21:28+00:00</updated>
<author>
<name>Tom Lane</name>
<email>tgl@sss.pgh.pa.us</email>
</author>
<published>2006-10-11T20:21:28+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/postgresql.git/commit/?id=47cec0327eba5dc069f8b6ad851275b5edf7ff2f'/>
<id>47cec0327eba5dc069f8b6ad851275b5edf7ff2f</id>
<content type='text'>
I introduced in 7.4.1 :-(.  It's correct to allow unknown to be coerced to
ANY or ANYELEMENT, since it's a real-enough data type, but it most certainly
isn't an array datatype.  This can cause a backend crash but AFAICT is not
exploitable as a security hole.  Per report from Michael Fuhr.

Note: as fixed in HEAD, this changes a constant in the pg_stats view,
resulting in a change in the expected regression outputs.  The back-branch
patches have been hacked to avoid that, so that pre-existing installations
won't start failing their regression tests.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
I introduced in 7.4.1 :-(.  It's correct to allow unknown to be coerced to
ANY or ANYELEMENT, since it's a real-enough data type, but it most certainly
isn't an array datatype.  This can cause a backend crash but AFAICT is not
exploitable as a security hole.  Per report from Michael Fuhr.

Note: as fixed in HEAD, this changes a constant in the pg_stats view,
resulting in a change in the expected regression outputs.  The back-branch
patches have been hacked to avoid that, so that pre-existing installations
won't start failing their regression tests.
</pre>
</div>
</content>
</entry>
<entry>
<title>CREATE TABLE ... LIKE ... should mark the columns it creates with</title>
<updated>2006-10-11T20:03:26+00:00</updated>
<author>
<name>Tom Lane</name>
<email>tgl@sss.pgh.pa.us</email>
</author>
<published>2006-10-11T20:03:26+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/postgresql.git/commit/?id=1c2d02c499b3b7fac1b2bbc9a7e00cc97eaa5886'/>
<id>1c2d02c499b3b7fac1b2bbc9a7e00cc97eaa5886</id>
<content type='text'>
attislocal = true, since they are not really inherited but merely copied
from the original table.  I'm not sure if there are any cases where it makes
a real difference given the existing uses of the flag, but wrong is wrong.
This was fixed in passing in HEAD by the LIKE INCLUDING CONSTRAINTS patch,
but never back-patched.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
attislocal = true, since they are not really inherited but merely copied
from the original table.  I'm not sure if there are any cases where it makes
a real difference given the existing uses of the flag, but wrong is wrong.
This was fixed in passing in HEAD by the LIKE INCLUDING CONSTRAINTS patch,
but never back-patched.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix psql \d commands to behave properly when a pattern using regex | is given.</title>
<updated>2006-10-10T16:15:37+00:00</updated>
<author>
<name>Tom Lane</name>
<email>tgl@sss.pgh.pa.us</email>
</author>
<published>2006-10-10T16:15:37+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/postgresql.git/commit/?id=7b165e3ba54da7c845bb0f7236fcb08656361a96'/>
<id>7b165e3ba54da7c845bb0f7236fcb08656361a96</id>
<content type='text'>
Formerly they'd emit '^foo|bar$' which is wrong because the anchors are
parsed as part of the alternatives; must emit '^(foo|bar)$' to get expected
behavior.  Same as bug found previously in similar_escape().  Already fixed
in HEAD, this is just back-porting the part of that patch that was a bug fix.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Formerly they'd emit '^foo|bar$' which is wrong because the anchors are
parsed as part of the alternatives; must emit '^(foo|bar)$' to get expected
behavior.  Same as bug found previously in similar_escape().  Already fixed
in HEAD, this is just back-porting the part of that patch that was a bug fix.
</pre>
</div>
</content>
</entry>
<entry>
<title>Update libpq.rc for 7.3.16 and 7.4.14.  Later releases use libpq.rc.in,</title>
<updated>2006-10-10T00:19:58+00:00</updated>
<author>
<name>Bruce Momjian</name>
<email>bruce@momjian.us</email>
</author>
<published>2006-10-10T00:19:58+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/postgresql.git/commit/?id=f3fa771ccf905ad1c1c2ab6bfab7ece0c02bef39'/>
<id>f3fa771ccf905ad1c1c2ab6bfab7ece0c02bef39</id>
<content type='text'>
which was already updated.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
which was already updated.
</pre>
</div>
</content>
</entry>
<entry>
<title>Stamp releases 7.3.16, 7.4.14, 8.0.9, and 8.1.5.</title>
<updated>2006-10-09T23:38:34+00:00</updated>
<author>
<name>Bruce Momjian</name>
<email>bruce@momjian.us</email>
</author>
<published>2006-10-09T23:38:34+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/postgresql.git/commit/?id=10d46101f9d2edc41fbe92dab1959fcc2326fd1a'/>
<id>10d46101f9d2edc41fbe92dab1959fcc2326fd1a</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Update release notes for releases 7.3.16, 7.4.14, 8.0.9, and 8.1.5.</title>
<updated>2006-10-09T23:23:11+00:00</updated>
<author>
<name>Bruce Momjian</name>
<email>bruce@momjian.us</email>
</author>
<published>2006-10-09T23:23:11+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/postgresql.git/commit/?id=f18ace69dc9e3c95399784c4d954f6c43bac8a23'/>
<id>f18ace69dc9e3c95399784c4d954f6c43bac8a23</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix back-branch pg_regress scripts to try the "canonical" expected file if we</title>
<updated>2006-10-09T01:45:57+00:00</updated>
<author>
<name>Tom Lane</name>
<email>tgl@sss.pgh.pa.us</email>
</author>
<published>2006-10-09T01:45:57+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/postgresql.git/commit/?id=b1bc5d5ddafe0fa8431020dcb32729098b110a72'/>
<id>b1bc5d5ddafe0fa8431020dcb32729098b110a72</id>
<content type='text'>
tried a variant file from resultmap and it didn't match.  This is already done
in HEAD's C-code version, and is needed because OpenBSD has recently migrated
to a more standard handling of float underflow --- see buildfarm results
from emu.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
tried a variant file from resultmap and it didn't match.  This is already done
in HEAD's C-code version, and is needed because OpenBSD has recently migrated
to a more standard handling of float underflow --- see buildfarm results
from emu.
</pre>
</div>
</content>
</entry>
<entry>
<title>Fix ancient oversight in psql's \d pattern processing code: when seeing two</title>
<updated>2006-10-07T22:21:57+00:00</updated>
<author>
<name>Tom Lane</name>
<email>tgl@sss.pgh.pa.us</email>
</author>
<published>2006-10-07T22:21:57+00:00</published>
<link rel='alternate' type='text/html' href='http://trove.baserock.org/cgit/delta/postgresql.git/commit/?id=d85820cfb2ca90929a799f873ba6f07f8a553846'/>
<id>d85820cfb2ca90929a799f873ba6f07f8a553846</id>
<content type='text'>
quote chars inside quote marks, should emit one quote *and stay in inquotes
mode*.  No doubt the lack of reports of this have something to do with the
poor documentation of the feature ...
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
quote chars inside quote marks, should emit one quote *and stay in inquotes
mode*.  No doubt the lack of reports of this have something to do with the
poor documentation of the feature ...
</pre>
</div>
</content>
</entry>
</feed>
