| Commit message (Collapse) | Author | Age |
|
|
|
| |
(surprised no one has reported these yet...)
|
|
|
|
|
|
| |
are correct, consistent, and complete ... motivated by gripe from
Oliver Elphick, but I see someone had already made an incomplete stab
at this.
|
| |
|
| |
|
|
|
|
|
|
| |
should be accounted for in the PROC_SEM_MAP_ENTRIES() macro. Otherwise
the ports that rely on this macro to size data structures are broken.
Mea culpa.
|
|
|
|
| |
Need to return a TupleTableSlot, not just a bare tuple.
|
|
|
|
| |
initdb/regression tests pass.
|
|
|
|
|
|
|
|
|
| |
to the target list in gram.y; it must wait till after expansion of the
target list in analyze.c. Per bug report 4-Nov:
lx=# CREATE TABLE abc (a char, b char, c char);
CREATE
lx=# CREATE TABLE xyz (x, y, z) AS SELECT * FROM abc;
ERROR: CREATE TABLE/AS SELECT has mismatched column count
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
so that only one signal number is used not three. Flags in shared
memory tell the reason(s) for the current signal. This method is
extensible to handle more signal reasons without chewing up even more
signal numbers, but the immediate reason is to keep pg_pwd reloads
separate from SIGHUP processing in the postmaster.
Also clean up some problems in the postmaster with delayed response to
checkpoint status changes --- basically, it wouldn't schedule a checkpoint
if it wasn't getting connection requests on a regular basis.
|
|
|
|
|
| |
UNIQUE-PRIMARY KEY notice message. This is what Christopher wanted from
his patch.
|
|
|
|
|
| |
same code is called for both creation and alter. Not worth worrying
about.
|
|
|
|
|
|
| |
analysis. This keeps stored rules from prematurely absorbing default
information, which is necessary for ALTER TABLE SET DEFAULT to work
unsurprisingly with rules. See pgsql-bugs discussion 24-Oct-01.
|
|
|
|
|
|
|
| |
postmaster children before client auth step. Postmaster now rereads
pg_pwd on receipt of SIGHUP, the same way that pg_hba.conf is handled.
No cycles need be expended to validate password cache validity during
connection startup.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
recreated since the start of our transaction, our first reference to it
errored out because we'd try to reuse our old relcache entry for it.
Do this by accepting SI inval messages just before relcache search in
heap_openr, so that dead relcache entries will be flushed before we
search. Also, break heap_open/openr into two pairs of routines,
relation_open(r) and heap_open(r). The relation_open routines make
no tests on relkind and so can be used to open anything that has a
pg_class entry. The heap_open routines are wrappers that add a relkind
test to preserve their established behavior. Use the relation_open
routines in several places that had various kluge solutions for opening
rels that might be either heap or index rels.
Also, remove the old 'heap stats' code that's been superseded by Jan's
stats collector, and clean up some inconsistencies in error reporting
between the different types of ALTER TABLE.
|
| |
|
|
|
|
|
|
| |
stored in pg_pwd, to guard against failures of the sort observed by
Tom Yackel. Note: in the case of encrypted passwords this is no
restriction, since the string we are interested in is the MD5 hash.
|
| |
|
| |
|
| |
|
|
|
|
| |
message spacing.
|
|
|
|
|
|
|
|
| |
which incorporates recent changes by Bruce to
readability of some messages and few more translations.
--
Serguei A. Mokhov
|
|
|
|
|
|
| |
Add space between slash for ALTER TABLE / ADD ....
Regression and *.po updates to follow.
|
|
|
|
|
|
| |
from Philip Warner. Side effect of change is that GROUP BY expressions
will not be re-evaluated at multiple plan levels anymore, whereas this
sometimes happened with old code.
|
| |
|
| |
|
| |
|
|
|
|
| |
spacing. Also adds space for one-line comments.
|
|
|
|
|
| |
causes pgindent to make weird formatting decisions. Easiest fix
seems to be to put in the extra parens...
|
|
|
|
|
| |
breaking existing pg_dump scripts, which try to assign the result of
count(*) to an int2 variable. catversion bumped.
|
| |
|
|
|
|
| |
tests pass.
|
| |
|
|
|
|
| |
forth@pagic.net
|
| |
|
| |
|
| |
|
|
|
|
| |
user columns. Needed for foreign keys on OID, but useful in general.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
never overwrite adjacent pages with copied data, even if page header
and/or item pointers are already corrupt. Change inspired by trouble
report from Alvaro Herrera.
|
|
|
|
| |
for indexes on system columns. Per complaint from Peter.
|
| |
|
|
|
|
|
|
|
|
| |
environment strings need to be moved around, do so when called from
initial startup (main.c), not in init_ps_status. This eliminates the
former risk of invalidating saved environment-string pointers, since
no code has yet had a chance to grab any such pointers when main.c
is running.
|
|
|
|
|
| |
arguments (where the parser doesn't check them already). Minor code
cleanups too.
|
|
|
|
| |
in .:/home/postgres/testversion/bin:/opt/perl5.6.1/bin:/home/postgres/bin:/usr/local/bin:/usr/bin:/opt/ansic/bin:/usr/ccs/bin:/usr/contrib/bin:/opt/nettladm/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/upgrade/bin:/opt/CC/bin:/opt/langtools/bin:/opt/graphics/phigs/bin:/opt/java/bin:/bin:/opt/imake/bin:/opt/hparray/bin:/opt/aCC/bin:/opt/lrom/bin:/usr/local/nmh/bin:. (I suppose the only common case for this is '.').
|
|
|
|
|
|
| |
per suggestion from Peter. Simplify several APIs by transmitting the
original argv location directly from main.c to ps_status.c, instead of
passing it down through several levels of subroutines.
|
| |
|