Log Message:
---
Minor SGML markup cleanup.
Modified Files:
--
pgsql/doc/src/sgml:
func.sgml (r1.257 -> r1.258)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.257&r2=1.258)
---(end of broadcast)--
Bruce Momjian wrote:
Add pg_postmaster_start_time() function.
You should have bumped the catversion, no?
-Neil
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Log Message:
---
Remove old *.backup files when we do pg_stop_backup(). This
prevents a large number of *.backup files from existing in pg_xlog/
Modified Files:
--
pgsql/src/backend/access/transam:
xlog.c (r1.199 -> r1.200)
(http://developer.postgresql.org
Log Message:
---
Mention we now support BETWEEN SYMMETRIC.
Christopher Kings-Lynne
Modified Files:
--
pgsql/src/backend/catalog:
sql_features.txt (r1.12 -> r1.13)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/sql_features.txt.diff?r
Log Message:
---
This patch makes it possible to use the full set of timezones when doing
"AT TIME ZONE", and not just the shorlist previously available. For
example:
SELECT CURRENT_TIMESTAMP AT TIME ZONE 'Europe/London';
works fine now. It will also obey whatever DST rules were in effect
Log Message:
---
> Here's a patch I added against plperl, originally against beta5, now
> against rc1. It simply checks with GetDatabaseEncoding() if the current
> database is in UTF-8, and if so, sets the UTF-8 flag on the arguments
> that are passed to perl. This means that it isn't neces
Log Message:
---
Support 3 and 4-byte unicode characters.
John Hansen
Modified Files:
--
pgsql/src/backend/utils/mb:
conv.c (r1.52 -> r1.53)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/mb/conv.c.diff?r1=1.52&r2=1.53)
wchar.c
Log Message:
---
>> Do you agree that using a hashtable for it in general is a good idea
>> assuming this sideeffect is removed, though?
>
>I have no problem with the hashtable, only with preloading it with
>everything. What I'd like to see is that the table inherited at fork()
>contains j
Log Message:
---
Now \d show tablespace of indices per discussion.
test=# \d e
Table "public.e"
Column | Type | Modifiers
+-+---
i | integer | not null
j | integer | not null
k | integer |
Indexes:
"e_pkey" PRIMARY KEY, btree (i, j),
Log Message:
---
Add BETWEEN SYMMETRIC.
Pavel Stehule
Modified Files:
--
pgsql/doc/src/sgml:
func.sgml (r1.255 -> r1.256)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.255&r2=1.256)
pgsql/src/backend/parser:
Log Message:
---
Done:
> * -Add BETWEEN ASYMMETRIC/SYMMETRIC
Modified Files:
--
pgsql/doc:
TODO (r1.1561 -> r1.1562)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1561&r2=1.1562)
pgsql/doc/src/FAQ:
TODO.html (r1.68 -> r1.
Log Message:
---
reorder:
< * -Add BETWEEN ASYMMETRIC/SYMMETRIC
> * -Add BETWEEN SYMMETRIC/ASYMMETRIC
Modified Files:
--
pgsql/doc:
TODO (r1.1562 -> r1.1563)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1562&r2=1.1563)
pgsql/doc/
Log Message:
---
Use ' ' escapes for leading spaces in table values, for use in
EXPLAIN output.
Jean-Paul Argudo
Modified Files:
--
pgsql/src/bin/psql:
print.c (r1.59 -> r1.60)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/print.c.diff?r1=
Log Message:
---
Simplify shared-memory lock data structures as per recent discussion:
it is sufficient to track whether a backend holds a lock or not, and
store information about transaction vs. session locks only in the
inside-the-backend LocalLockTable. Since there can now be but one
PR
Log Message:
---
Add pg_postmaster_start_time() function.
Euler Taveira de Oliveira
Matthias Schmidt
Modified Files:
--
pgsql/doc/src/sgml:
func.sgml (r1.254 -> r1.255)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/func.sgml.diff?r1=1.254&
Log Message:
---
Initialize the call's expectation to the function's return type. This will be
overloaded if rsi->expectedDesc != NULL. (fixes a bug where it attempts to call
None on return)
Modified Files:
--
be/src/call:
pl.c (r1.7 -> r1.8)
(http://cvs.pg
Log Message:
---
Done:
> o -Have SHOW ALL show descriptions for server-side variables
Modified Files:
--
pgsql/doc:
TODO (r1.1560 -> r1.1561)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1560&r2=1.1561)
pgsql/doc/src/FAQ:
Log Message:
---
Have SHOW ALL include variable descriptions.
Matthias Schmidt
Modified Files:
--
pgsql/doc/src/sgml/ref:
show.sgml (r1.38 -> r1.39)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/show.sgml.diff?r1=1.38&r2=1.39)
pgsq
Log Message:
---
Update:
< o Have SHOW ALL and pg_settings show descriptions for server-side
variables
> o Have SHOW ALL show descriptions for server-side variables
Modified Files:
--
pgsql/doc:
TODO (r1.1559 -> r1.1560)
(http://developer.post
Log Message:
---
Move item into proper section:
o Have SHOW ALL and pg_settings show descriptions for server-side
variables
Modified Files:
--
pgsql/doc:
TODO (r1.1558 -> r1.1559)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=
Log Message:
---
Attached is a makefile I hacked up to build pg_config under MSVC - the
reason is that it's required (more or less) in order to build the latest
DBD::Pg code and I was testing that out under MSVC.
Andrew Dunstan
Modified Files:
--
pgsql/src:
win32.m
Log Message:
---
Add GUC krb_server_hostname so the server hostname can be specified as
part of service principal. If not set, any service principal matching
an entry in the keytab can be used.
NEW KERBEROS MATCHING BEHAVIOR FOR 8.1.
Todd Kover
Modified Files:
--
pgsql/d
Log Message:
---
Done:
> o -Allow PL/PgSQL's RAISE function to take expressions
Modified Files:
--
pgsql/doc:
TODO (r1.1557 -> r1.1558)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO.diff?r1=1.1557&r2=1.1558)
pgsql/doc/src/FAQ:
Log Message:
---
The random selection in function linear() could deliver a value equal to max
if geqo_rand() returns exactly 1.0, resulting in failure due to indexing
off the end of the pool array. Also, since this is using inexact float math,
it seems wise to guard against roundoff error
Log Message:
---
The random selection in function linear() could deliver a value equal to max
if geqo_rand() returns exactly 1.0, resulting in failure due to indexing
off the end of the pool array. Also, since this is using inexact float math,
it seems wise to guard against roundoff error
Log Message:
---
The random selection in function linear() could deliver a value equal to max
if geqo_rand() returns exactly 1.0, resulting in failure due to indexing
off the end of the pool array. Also, since this is using inexact float math,
it seems wise to guard against roundoff error
Log Message:
---
The random selection in function linear() could deliver a value equal to max
if geqo_rand() returns exactly 1.0, resulting in failure due to indexing
off the end of the pool array. Also, since this is using inexact float math,
it seems wise to guard against roundoff error
Log Message:
---
The random selection in function linear() could deliver a value equal to max
if geqo_rand() returns exactly 1.0, resulting in failure due to indexing
off the end of the pool array. Also, since this is using inexact float math,
it seems wise to guard against roundoff error
Log Message:
---
WAL for GiST. It work for online backup and so on, but on
recovery after crash (power loss etc) it may say that it can't restore
index and index should be reindexed.
Some refactoring code.
Modified Files:
--
pgsql/src/backend/access/gist:
Makefil
29 matches
Mail list logo
