| Commit message (Collapse) | Author | Age |
|
|
|
| |
configuration options `Log_timestamp' and `Log_pid'.
|
|
|
|
|
|
| |
Install a default configuration file.
Clean up some funny business in the config file code.
|
| |
|
|
|
|
| |
"rb" and "wb".
|
| |
|
|
|
|
|
| |
to do it at the last moment before calling system() ... not at some
randomly-chosen earlier point in the routine ...
|
|
|
|
|
|
|
|
|
|
| |
it will close VFDs if necessary to surmount ENFILE or EMFILE failures.
Make use of this in md.c, xlog.c, and user.c routines that were
formerly vulnerable to these failures. In particular, this should
handle failures of mdblindwrt() that have been observed under heavy
load conditions. (By golly, every other process on the system may
crash after Postgres eats up all the kernel FDs, but Postgres will
keep going!)
|
|
|
|
|
| |
conditional expression x?y:z in an awk program. Seems old versions
of awk don't have that ...
|
| |
|
|
|
|
| |
overlength quoted identifiers. Death and destruction ensue...
|
|
|
|
|
|
| |
the prototype in guc.h. The following patch corrects that.
Billy G. Allie
|
|
|
|
| |
some versions of gmake (mine didn't do the right thing, anyway).
|
|
|
|
|
|
|
| |
(ie, parameters instead of consts) will be treated as a range query.
We do not know the actual selectivities involved, but it seems like
a good idea to use a smaller estimate than we would use for two unrelated
inequalities.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
That means you can now set your options in either or all of $PGDATA/configuration,
some postmaster option (--enable-fsync=off), or set a SET command. The list of
options is in backend/utils/misc/guc.c, documentation will be written post haste.
pg_options is gone, so is that pq_geqo config file. Also removed were backend -K,
-Q, and -T options (no longer applicable, although -d0 does the same as -Q).
Added to configure an --enable-syslog option.
changed all callers from TPRINTF to elog(DEBUG)
|
| |
|
| |
|
|
|
|
| |
AUTHTYPE in config file. Patch both branches.
|
| |
|
|
|
|
| |
trial implementation.
|
|
|
|
|
| |
fmgr_faddr() in favor of new-style calls. Lots of cleanup of
sloppy casts to use XXXGetDatum and DatumGetXXX ...
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
built-in procedures are named after the prosrc field of pg_proc (ie,
the actual C function name), not the proname field. This did not use
to make a difference back when the two were always the same, but in the
presence of overloaded proname values we'd best try to use the C name
instead. AFAICT this change affects no existing code, but it is
necessary to be able to get at some built-in functions that no macro
was being generated for before.
|
|
|
|
|
|
| |
to 10, and be consistent about whether it counts the trailing null (it
does not). Also increase MAXDATELEN to be sure no buffer overflows are
caused by the longer MAXTZLEN.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
the src/include tree, so that -I backend is no longer necessary anywhere.
Also, clean up some bit rot in contrib tree.
|
|
|
|
| |
CurrentTriggerData is history.
|
| |
|
| |
|
|
|
|
| |
pg_language entries.
|
|
|
|
|
| |
that have at least one constant-NULL input, even if other inputs are
not constants.
|
|
|
|
| |
Need to update user docs still ...
|
|
|
|
|
|
|
| |
key call sites are changed, but most called functions are still oldstyle.
An exception is that the PL managers are updated (so, for example, NULL
handling now behaves as expected in plperl and plpgsql functions).
NOTE initdb is forced due to added column in pg_proc.
|
|
|
|
|
| |
necessary to call isatty() for each and every received query. That's
one less kernel call per query cycle ...
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most (nearly all) of the work was done by David Wragg <dpw@doc.ic.ac.uk>
He patched 6.5.3. I've updated it for 7.0RC5.
It works for MIT kerberos 1.1.1 (and previously for 1.0.6 as well).
I've got the patch against 6.5.3, plus kerberized RPMS.
Mike Wyer <mw@doc.ic.ac.uk> || "Woof?"
|
| |
|
| |
|
|
|
|
|
|
|
| |
other than the most common value in a column. We had had 0.5, make it
0.1 to make it more likely that an indexscan will be chosen. Really
need better statistics instead, but this should stem the bleeding
meanwhile ...
|
| |
|