| Age | Commit message (Collapse) | Author |
|---|
|
< * %Disallow changing sequence characteristics like INCREMENT for SERIAL columns
> * %Disallow ALTER SEQUENCE changes for SERIAL sequences because pg_dump
> does not dump the changes
|
|
> * %Disallow changing sequence characteristics like INCREMENT for SERIAL columns
|
|
|
|
returning "ASCII code of the first character of the argument"
(see
http://www.postgresql.org/docs/8.1/interactive/functions-string.html,
Table 9-6. "Other String Functions").
Presumably this should read "ASCII code of the first byte of the
argument",
which is what is returned when the argument is a multi-byte character
(although then with UTF-8 at least that might not necessarily be an
ASCII
code).
Ian Barwick
|
|
statements before the multi-line statement, rather than inside the
multi-line statement.
|
|
columns of the grouping clause to avoid redundant sorts. The optimizer
is not currently capable of doing this, so this patch implements a
simple hack in the analysis phase (transformGroupClause): if any
subset of the GROUP BY clause matches a prefix of the ORDER BY list,
that prefix is moved to the front of the GROUP BY clause. This
shouldn't change the semantics of the query, and allows a redundant
sort to be avoided for queries like "GROUP BY a, b ORDER BY b".
|
|
> o Port contrib/xml2
|
|
and docs from Dmitry Karasik, slightly editorialised.
|
|
|
|
|
|
> o -Add "include file" functionality in postgresql.conf
|
|
variable.
|
|
Add DLLIMPORT for V1 headers, in case Win32 don't export all symbols.
|
|
example of /etc/sysctl.conf contents.
|
|
Patch by Joachim Wieland, somewhat reworked for clarity and portability.
|
|
This is consistent with the standard definition of fopen().
|
|
In particular, ensure that enlargement of the memtuples[] array doesn't
fall foul of MaxAllocSize when work_mem is very large, and don't bother
enlarging it if that would force an immediate switch into 'tape' mode anyway.
|
|
per report from Stefan Kaltenbrunner.
|
|
we'll go over to disk-based sort if we reach that limit.
This fixes Stefan Kaltenbrunner's observation that sorting can suffer an
'invalid memory alloc request size' failure when sort_mem is set large
enough. It's unfortunately not so easy to fix in 8.1 ...
|
|
sequence such as "0x95 0x27". Patches from Akio Ishida.
Also update copyright notice.
|
|
> * Allow FSM page return free space based on table clustering, to assist
> in maintaining clustering?
|
|
> type
Wouldn't it be better to use the UINT64CONST macro? I realize this
file is Windows-only, but we do worry about more than one compiler
on that platform.
Kris Jurka
|
|
> just that certain commands do. TRUNCATE isn't shown.
Patch against HEAD to add TRUNCATE to the list of commands that aquire
ACCESS EXCLUSIVE.
Jim C. Nasby, Sr.
|
|
|
|
descriptions after the code are correct). Only shmmax needs to be
multiples of the page size (at least, that's how I interpret the
Darwin code).
Chris Campbell
|
|
gettimeofday.c:35: warning: integer constant is too large for "long"
type
Kris Jurka
|
|
/dev/tty, but it isn't a device file and doesn't work as expected.
This fixes a known bug where psql does not prompt for a password on some
Win32 systems.
Backpatch to 8.1.X.
Robert Kinberg
|
|
instead of the old deprecated ones.
Volkan Yazici, with some editorializing by moi.
|
|
Hiroshi Saito
|
|
|
|
|
|
have. This happens when MSVC uses pg_config.h generated by MinGW.
Per report from Charles F. I. Savage
|
|
and tighten up its sanity checking of the tag as a safety measure.
Volkan Yazici.
|
|
|
|
> * -Allow TRUNCATE ... CASCADE/RESTRICT
|
|
< o %Have COPY return the number of rows loaded/unloaded?
> o -Have COPY return the number of rows loaded/unloaded?
|
|
rows copied. Backend side of Volkan Yazici's recent patch, with
corrections and documentation.
|
|
relations are still checked for permissions etc as soon as they are
opened. The original form of the patch could hold exclusive lock for a
long time on relations that the user doesn't even have permissions to
access, let alone truncate.
|
|
Fixes problem with 'su' on some platforms.
|
|
|
|
|
|
> * Allow FSM to return free space toward the beginning of the heap file,
> in hopes that empty pages at the end can be truncated by VACUUM
|
|
ROLE page, based on what Tom Lane told me here:
http://archives.postgresql.org/pgsql-general/2005-11/msg00998.php
Joachim Wieland
|
|
> * Add missing parameter handling in to_char()
>
> http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php
>
|
|
> * Allow to_date() and to_timestamp() accept localized month names
|
|
|
|
checkpoint in the bgwriter. This forestalls overflow of the fsync request
queue, which is not fatal but causes considerable performance degradation
when it occurs (because backends then have to do their own fsyncs). Per
patch from Itagaki Takahiro, modified a little bit by me.
|
|
a need for it back in the neolithic era, but it's certainly dead code in
any PG release we would recognize as such. Since it forces an additional
network round trip to the backend, getting rid of it should provide some
small performance improvement for large-object-using clients.
|
|
was opening with INV_READ flag and then writing. Prior to 8.1 the backend
did not reject this, but now it does.
|
|
them to use array_recv :-(. Per report from Tim Kordas.
|
