Log Message:
---
Update URL for set-returning functions.
Modified Files:
--
pgsql/doc:
FAQ (r1.414 -> r1.415)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ.diff?r1=1.414&r2=1.415)
pgsql/doc/src/FAQ:
FAQ.html (r1.370 -> r1.371)
Log Message:
---
Allow pltcl args to spi_prepare and plpython args to plpy.prepare to be
standard type aliases as well as those known in pg_type. Similar to recent
change in plperl.
Modified Files:
--
pgsql/doc/src/sgml:
pltcl.sgml (r2.45 -> r2.46)
(http:
Log Message:
---
Add URL for:
o Allow row and record variables to be set to NULL constants,
and allow NULL tests on such variables
Modified Files:
--
pgsql/doc:
TODO (r1.2115 -> r1.2116)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/T
Log Message:
---
Prevent BLCKSZ < 1024, and have initdb test shared buffers based on the
BLCKSZ value.
Modified Files:
--
pgsql/src/bin/initdb:
initdb.c (r1.133 -> r1.134)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/initdb/initdb.c.diff?r1=1.1
Log Message:
---
Add:
>
> * Consider decreasing the amount of memory used by PrivateRefCount
>
> http://archives.postgresql.org/pgsql-hackers/2006-11/msg00797.php
> http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php
>
Modified Files:
--
pgsql/doc:
Log Message:
---
Fix markup.
Modified Files:
--
pgsql/doc/src/sgml:
information_schema.sgml (r1.32 -> r1.33)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/information_schema.sgml.diff?r1=1.32&r2=1.33)
---(end of bro
Log Message:
---
Change $(CC) to $(COMPILER) on Solaris gcc so -m64 is passed into the
shared link line.
Modified Files:
--
pgsql/src:
Makefile.shlib (r1.108 -> r1.109)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/Makefile.shlib.diff?r1=1.108&r2=1.
Log Message:
---
Add:
> * Increase locking when DROPing objects so dependent objects cannot
> get dropped while the DROP operation is happening
>
> http://archives.postgresql.org/pgsql-hackers/2007-01/msg00937.php
Modified Files:
--
pgsql/doc:
TODO (r1.2113 ->
Log Message:
---
Add URL for:
o Allow UPDATE/DELETE WHERE CURRENT OF cursor
> http://archives.postgresql.org/pgsql-hackers/2007-01/msg01014.php
Modified Files:
--
pgsql/doc:
TODO (r1.2112 -> r1.2113)
(http://developer.postgresql.org/cvsweb.
Log Message:
---
Add:
>
> * Add missing operators for geometric data types
>
> Some geometric types do not have the full suite of geometric operators,
> e.g. box @> point
>
Modified Files:
--
pgsql/doc:
TODO (r1.2111 -> r1.2112)
(http://developer.pos
Peter Eisentraut wrote:
> Am Dienstag, 20. Februar 2007 19:47 schrieb Bruce Momjian:
> > Log Message:
> > ---
> > Update information_schema documentation to match system tables.
> > Backpatch to 8.2.X.
>
> The columns affected by this patch do not appear in the system tables. What
> is t
Am Dienstag, 20. Februar 2007 19:47 schrieb Bruce Momjian:
> Log Message:
> ---
> Update information_schema documentation to match system tables.
> Backpatch to 8.2.X.
The columns affected by this patch do not appear in the system tables. What
is the real purpose of this change?
--
Pet
Dave Page wrote:
If you are savvy enough to read the docs, un-hide the directory, and
manually create the file in the correct format, surely you can also run
cacls on it? We expect *nix users to run chmod on theirs after all.
I don't see this as such a big issue.
I think this is OK if we
Magnus Hagander wrote:
> Dave Page wrote:
>> Magnus Hagander wrote:
>>> It would break insofar that it wouldn't work. the pgpass file. It will
>>> of course not break *windows*, but people will consider PostgreSQL broken.
>>>
>> Please explain why it won't work. *Existing* pgpass files would need t
Dave Page wrote:
> Magnus Hagander wrote:
>> It would break insofar that it wouldn't work. the pgpass file. It will
>> of course not break *windows*, but people will consider PostgreSQL broken.
>>
>
> Please explain why it won't work. *Existing* pgpass files would need to
> be secured, but that co
Log Message:
---
Update "encode" documentation to mention that 'escape' only changes null
bytes and backslashes, remove "ASCII" mention. Backpatch to 8.2.X.
Modified Files:
--
pgsql/doc/src/sgml:
func.sgml (r1.368 -> r1.369)
(http://developer.postgresql.or
Magnus Hagander wrote:
>
> It would break insofar that it wouldn't work. the pgpass file. It will
> of course not break *windows*, but people will consider PostgreSQL broken.
>
Please explain why it won't work. *Existing* pgpass files would need to
be secured, but that could be handled with docu
Log Message:
---
Update "encode" documentation to mention that 'escape' only changes null
bytes and backslashes, remove "ASCII" mention. Backpatch to 8.2.X.
Tags:
REL8_2_STABLE
Modified Files:
--
pgsql/doc/src/sgml:
func.sgml (r1.347.2.5 -> r1.347.2.6)
Andrew Dunstan wrote:
> Dave Page wrote:
>> I think the only thing you could do would be to specify that the user
>> and only the user have full control over the file. *Any* other ACL
>> entries, deny or allow, are not allowed. Access via a group is not
>> allowed.
>>
>
>
> Are these condition
>>> I think the only thing you could do would be to specify that the user
>>> and only the user have full control over the file. *Any* other ACL
>>> entries, deny or allow, are not allowed. Access via a group is not allowed.
>> That will break every default install in the world. They will all
>> co
Dave Page wrote:
I think the only thing you could do would be to specify that the user
and only the user have full control over the file. *Any* other ACL
entries, deny or allow, are not allowed. Access via a group is not allowed.
Are these conditions true of the default location? If not, th
Magnus Hagander wrote:
> Well, if you don't trust your app, why are you running it ;-)
Theres a world of difference between trusting your app and knowing what
it's doing.
>>> Which would bring is to the "how". If there was an easy way to do the
>>> how, we should probably do it. However, I'm ver
I updated the documentation to say:
On Microsoft Windows, it is assumed that the file is stored in a
directory that is secure, so no special permissions check is made.
This might be as good as we can get.
--
Log Message:
---
Update pgpass Win32 wording.
Modified Files:
--
pgsql/doc/src/sgml:
libpq.sgml (r1.233 -> r1.234)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/libpq.sgml.diff?r1=1.233&r2=1.234)
---(end of broadcas
Dave Page wrote:
> Magnus Hagander wrote:
PGPASSFILE takes a full path name, so you can put the file anywhere you
want. Just like on Unix.
>>> OK, so we _do_ need to check the permissions on pgpass on Win32, but we
>>> just don't know how to do that?
>>>
>> If we _need_ to check, I don't
Magnus Hagander wrote:
>>> PGPASSFILE takes a full path name, so you can put the file anywhere you
>>> want. Just like on Unix.
>> OK, so we _do_ need to check the permissions on pgpass on Win32, but we
>> just don't know how to do that?
>>
>
> If we _need_ to check, I don't know. If you've set PG
Log Message:
---
Update information_schema documentation to match system tables.
Backpatch to 8.2.X.
Tags:
REL8_2_STABLE
Modified Files:
--
pgsql/doc/src/sgml:
information_schema.sgml (r1.29 -> r1.29.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pg
Log Message:
---
Update information_schema documentation to match system tables.
Backpatch to 8.2.X.
Modified Files:
--
pgsql/doc/src/sgml:
information_schema.sgml (r1.31 -> r1.32)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/information_s
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Magnus Hagander wrote:
>> PGPASSFILE takes a full path name, so you can put the file anywhere you
>> want. Just like on Unix.
> OK, so we _do_ need to check the permissions on pgpass on Win32, but we
> just don't know how to do that?
We could ignore PGP
Bruce Momjian wrote:
Andrew Dunstan wrote:
Tom Lane wrote:
Log Message:
---
Adjust user-facing documentation to explain why we don't check pgpass
file permissions on Windows.
+On Microsoft Windows, the file is stored in a directory that is secure by
+default, so no sp
>> PGPASSFILE takes a full path name, so you can put the file anywhere you
>> want. Just like on Unix.
>
> OK, so we _do_ need to check the permissions on pgpass on Win32, but we
> just don't know how to do that?
>
If we _need_ to check, I don't know. If you've set PGPASSFILE to
something, then
Magnus Hagander wrote:
> Bruce Momjian wrote:
> > Andrew Dunstan wrote:
> >> Tom Lane wrote:
> >>> Log Message:
> >>> ---
> >>> Adjust user-facing documentation to explain why we don't check pgpass
> >>> file permissions on Windows.
> >>>
> >> +On Microsoft Windows, the file is stored in
Bruce Momjian wrote:
> Andrew Dunstan wrote:
>> Tom Lane wrote:
>>> Log Message:
>>> ---
>>> Adjust user-facing documentation to explain why we don't check pgpass
>>> file permissions on Windows.
>>>
>> +On Microsoft Windows, the file is stored in a directory that is secure by
>> +defaul
Andrew Dunstan wrote:
> Tom Lane wrote:
> > Log Message:
> > ---
> > Adjust user-facing documentation to explain why we don't check pgpass
> > file permissions on Windows.
> >
>
> +On Microsoft Windows, the file is stored in a directory that is secure by
> +default, so no special permis
Tom Lane wrote:
Log Message:
---
Adjust user-facing documentation to explain why we don't check pgpass
file permissions on Windows.
+On Microsoft Windows, the file is stored in a directory that is secure by
+default, so no special permissions check is made.
I doubt this is true if
Log Message:
---
Wording improvement.
Modified Files:
--
pgsql/doc/src/sgml:
func.sgml (r1.367 -> r1.368)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.367&r2=1.368)
---(end of broadcast)
Log Message:
---
More clearly document that most PostgreSQL utilities support libpq
environment variables. Backpatch to 8.2.X.
Tags:
REL8_2_STABLE
Modified Files:
--
pgsql/doc/src/sgml/ref:
clusterdb.sgml (r1.18 -> r1.18.2.1)
(http://developer.postgr
Log Message:
---
More clearly document that most PostgreSQL utilities support libpq
environment variables. Backpatch to 8.2.X.
Modified Files:
--
pgsql/doc/src/sgml/ref:
clusterdb.sgml (r1.18 -> r1.19)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/
Log Message:
---
Adjust user-facing documentation to explain why we don't check pgpass
file permissions on Windows.
Modified Files:
--
pgsql/doc/src/sgml:
libpq.sgml (r1.232 -> r1.233)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/libpq.sgm
Log Message:
---
Remove the Query structure from the executor's API. This allows us to stop
storing mostly-redundant Query trees in prepared statements, portals, etc.
To replace Query, a new node type called PlannedStmt is inserted by the
planner at the top of a completed plan tree; this c
Log Message:
---
Remove, item not needed for Win32:
< o Check .pgpass file permissions
>
Modified Files:
--
pgsql/doc:
TODO (r1.2110 -> r1.2111)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.2110&r2=1.2111)
pgsql/doc/src/FA
Log Message:
---
Add comment that on Win32, we don't need to check the .pgpass file
permission, per Magnus.
Modified Files:
--
pgsql/src/interfaces/libpq:
fe-connect.c (r1.343 -> r1.344)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq
Log Message:
---
Remove "History" sections for pg_dump and pg_restore. I don't think
anyone cares because the last history change was for PostgreSQL 7.1.
Modified Files:
--
pgsql/doc/src/sgml/ref:
pg_config-ref.sgml (r1.26 -> r1.27)
(http://developer.postg
Log Message:
---
Spell check on array patch.
Modified Files:
--
pgsql/doc/src/sgml:
array.sgml (r1.57 -> r1.58)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/array.sgml.diff?r1=1.57&r2=1.58)
---(end of broadcast)---
Log Message:
---
Spell check on array patch.
Tags:
REL8_2_STABLE
Modified Files:
--
pgsql/doc/src/sgml:
array.sgml (r1.52.2.2 -> r1.52.2.3)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/array.sgml.diff?r1=1.52.2.2&r2=1.52.2.3)
--
Log Message:
---
Add for WIN32:
<
> o Check .pgpass file permissions
Modified Files:
--
pgsql/doc:
TODO (r1.2109 -> r1.2110)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.2109&r2=1.2110)
pgsql/doc/src/FAQ:
TODO.htm
Log Message:
---
Update array slice documentation to be clearer.
Modified Files:
--
pgsql/doc/src/sgml:
array.sgml (r1.56 -> r1.57)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/array.sgml.diff?r1=1.56&r2=1.57)
---(
Log Message:
---
Update array slice documentation to be clearer.
Tags:
REL8_2_STABLE
Modified Files:
--
pgsql/doc/src/sgml:
array.sgml (r1.52.2.1 -> r1.52.2.2)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/array.sgml.diff?r1=1.52.2.1&
Log Message:
---
Add:
> * Fix IS OF so it matches the ISO specification, and add documentation
>
> http://archives.postgresql.org/pgsql-patches/2003-08/msg00060.php
> http://archives.postgresql.org/pgsql-hackers/2007-02/msg00060.php
Modified Files:
--
pgsql/doc:
Log Message:
---
Comment-out documentation for IS OF because it doesn't conform to the
ISO SQL behavior. Backpatch removal to 8.2.X.
Tags:
REL8_2_STABLE
Modified Files:
--
pgsql/doc/src/sgml:
func.sgml (r1.347.2.4 -> r1.347.2.5)
(http://developer.post
Log Message:
---
Comment-out documentation for IS OF because it doesn't conform to the
ISO SQL behavior. Backpatch removal to 8.2.X.
Modified Files:
--
pgsql/doc/src/sgml:
func.sgml (r1.366 -> r1.367)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/sr
Log Message:
---
Warn the user before deselecting dependency downloads.
Rank downloads after selection to ensure they get downloaded in the correct
order.
Modified Files:
--
wizard:
App.cpp (r1.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/stackb
Log Message:
---
Refactor tree handling to allow reloading should the user navigate backwards
through the wizard. Also ensure page validation on happens when moving forwards.
Modified Files:
--
wizard:
AppList.cpp (r1.1 -> r1.2)
(http://cvs.pgfoundry.org/c
Log Message:
---
Identify schema of inherited table in psql \d when necessary.
by Bernd Helmle
Modified Files:
--
pgsql/src/bin/psql:
describe.c (r1.151 -> r1.152)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/describe.c.diff?r1=1.151&r2=1
Log Message:
---
Add missing OIDs to pg_proc.
Modified Files:
--
pgsql/src/include/catalog:
catversion.h (r1.386 -> r1.387)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/include/catalog/catversion.h.diff?r1=1.386&r2=1.387)
pg_proc.h (r1.445
Log Message:
---
Add LongName attribute for xxid.v80.sql, per Raymond O'Donnell
Tags:
REL8_2_STABLE
Modified Files:
--
pginst/wxs:
pginst.wxs (r1.182.2.1 -> r1.182.2.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/pginst/wxs/pginst.wxs.dif
Log Message:
---
Add LongName attribute for xxid.v80.sql, per Raymond O'Donnell
Tags:
REL8_1_STABLE
Modified Files:
--
pginst/wxs:
pginst.wxs (r1.156.2.4 -> r1.156.2.5)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/pginst/wxs/pginst.wxs.dif
Log Message:
---
Add LongName attribute for xxid.v80.sql, per Raymond O'Donnell
Modified Files:
--
pginst/wxs:
pginst.wxs (r1.182 -> r1.183)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/pginst/wxs/pginst.wxs.diff?r1=1.182&r2=1.183)
58 matches
Mail list logo
