| Age | Commit message (Collapse) | Author |
|---|
|
a whole row or record variable into a SQL function. Eventually this case
should be made to actually work, but for now this is better than what it
did before.
|
|
is measured in kilobytes and checked against actual physical execution
stack depth, as per my proposal of 30-Dec. This gives us a fairly
bulletproof defense against crashing due to runaway recursive functions.
|
|
|
|
(errmsg("no socket configured for listening")));
|
|
with socket calls in signal handlers (APC) on Win32. See details in mail
to pgsql-hackers-win32 a couple of minutes ago.
Magnus Hagander
|
|
special Win32 open flag FILE_SHARE_DELETE.
Claudio Natoli
|
|
I have removed the docs mentioning that SSL and Kerberos are not
thread-safe.
Manfred Spraul
|
|
parameter description: postgresql.conf is not the place for
documentating the functionality of a GUC var.
|
|
>>equivalent to "-h localhost", shouldn't it?
>>
>>
>
>Now that is something I had not thought of. Seems we can assume a Win32
>psql can never use unix domain sockets, so defaulting that to localhost
>is a good solution too.
Andrew Dunstan
|
|
WITH/WITHOUT OIDS in dump files. This makes dump files more portable.
I have updated the pg_dump version so old binary dumps will load fine.
Pre-7.5 dumps use WITHOUT OIDS in SQL were needed, so they should be
fine.
|
|
and (in theory) QNX. Thanks to Chris KL for the report.
|
|
--disable-dollar-quoting.
Andrew Dunstan
|
|
in s_lock.c were not updated, and still refers to select. Made my grep
hit the wrong files, so I figured a simple patch was in order.. (other
refs in the same comment block was changed..)
Magnus Hagander
|
|
remove separate implementation of ALTER TABLE SET WITHOUT OIDS in favor
of doing a regular DROP. Also, cause CREATE TABLE to account completely
correctly for the inheritance status of the OID column. This fixes
problems with dropping OID columns that have dependencies, as noted by
Christopher Kings-Lynne, as well as making sure that you can't drop an
OID column that was inherited from a parent.
|
|
Fixed problem with pg_dump tar backups. Only happens on platforms that
use our port/fseeko.c, which is currently BSD/OS and NetBSD.
|
|
*result = getpwuid_r(uid, resultbuf, buffer, buflen);
|
|
listen_addresses parameter, as per recent discussion. The default behavior
is now to listen on localhost, which eliminates the need for the -i
postmaster switch in many scenarios.
Andrew Dunstan
|
|
ensure that it actually passes data. This catches cases such as a kernel
packet filter rule that makes the socket useless.
Andrew Dunstan
|
|
|
|
followup to complaint from Korean User's Group.
|
|
|
|
|
|
sequences and views). This patch allows it to handle views and
sequences.
Euler Taveira de Oliveira
|
|
Claudio Natoli
|
|
|
|
flesh out the index operator classes to include these. In passing,
fix erroneous volatility marking of ACL functions.
|
|
errors in internally-generated queries, such as those submitted by
plpgsql functions. Per recent discussions with Fabien Coelho.
|
|
|
|
|
|
in one query, rather than making a separate query for each object that
could have a comment. This costs relatively little space (a few tens of
K typically) and saves substantial time in databases with many objects.
I find it reduces the runtime of 'pg_dump -s regression' by about a
third.
|
|
|
|
Backpatch to 7.4.X. Required for Solaris 7 & 8.
|
|
is done at creation time for plpgsql functions. Improve createlang and
droplang to support adding/dropping validators for PLs. Initial steps
towards producing a syntax error position from plpgsql syntax errors
(this part is a work in progress, and will change depending on outcome
of current discussions).
|
|
of fighting it, avoid hard-wired (and wrong) assumption about max length
of prefix, cause %l to actually work as documented, don't compute data
we may not need.
|
|
|
|
|
|
|
|
|
|
Make open/close loop testings the same. Add descriptions for certain tests.
|
|
|
|
Compare fsync before and after write's close:
Compare one o_sync write to two:
Compare file sync methods with one 8k write:
Compare file sync methods with 2 8k writes:
|
|
|
|
|
|
|
|
|
|
same when done on the write() ile descriptor and a new descriptor.
it also times various fsync methods.
|
|
TID (heap position). This doesn't do anything to the validity of the
finished index, but by pretending to qsort() that there are no really
equal keys in the sort, we can avoid performance problems with qsort
implementations that have trouble with large numbers of equal keys.
Patch from Manfred Koizar.
|
|
so that the 'val' is computed only once, per recent discussion. The
speedup is not much when 'val' is just a simple variable, but could be
significant for larger expressions. More importantly this avoids issues
with multiple evaluations of a volatile 'val', and it allows the CASE
expression to be reverse-listed in its original form by ruleutils.c.
|
|
|
|
directly to the appropriate per-node execution function, using a function
pointer stored by ExecInitExpr. This speeds things up by eliminating one
level of function call. The function-pointer technique also enables further
small improvements such as only making one-time tests once (and then
changing the function pointer). Overall this seems to gain about 10%
on evaluation of simple expressions, which isn't earthshaking but seems
a worthwhile gain for a relatively small hack. Per recent discussion
on pghackers.
|
