| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A new pg_hba.conf column, USER
Allow specifiction of lists of users separated by commas
Allow group names specified by +
Allow include files containing lists of users specified by @
Allow lists of databases, and database files
Allow samegroup in database column to match group name matching dbname
Removal of secondary password files
Remove pg_passwd utility
Lots of code cleanup in user.c and hba.c
New data/global/pg_pwd format
New data/global/pg_group file
|
| |
|
|
|
|
| |
and/or with GUC variables.
|
|
|
|
|
| |
syslog when appropriate. These were the last perror() calls remaining
in the backend; let's not reintroduce any...
|
|
|
|
|
| |
per recent discussion on pghackers. Also, fix PGSTAT code to report
errors via elog, not scribbling directly on stderr.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
From: Bradley McLean <brad@bradm.net>
Patch against 7,2 submitted for comment.
This seems to work just fine; Now, when our users submit a 2 hour
query with four million row sorts by accident, then cancel it 30 seconds
later, it doesn't bog down the server ...
|
| |
|
|
|
|
| |
as argument for nextval().
|
|
|
|
| |
problem reported a few months ago where a select in a rule was causing an insert statement to return a result set which the code was explicitly prohibiting.
|
|
|
|
|
|
| |
wrapped-around databases. The unvacuumed databases might be fine, or
they might not, but things will definitely not be fine if we remove the
wrong CLOG segments. Per trouble report from Gary Wolfe, 1-Apr-2002.
|
| |
|
|
|
|
|
|
|
|
| |
depend on this rather than the trigger argument strings to locate the
other relation to test. This makes RI triggers function properly in
the presence of schemas and temp tables. Along the way, fix bogus lack
of locking in RI triggers, handle quoting of names fully correctly,
compute required sizes of query buffers with some semblance of accuracy.
|
|
|
|
|
|
|
| |
bootstrap/bootparse.y, so that recent versions of bison don't emit a
warning.
Neil Conway
|
| |
|
|
|
|
|
|
|
| |
path. The default behavior if no per-user schemas are created is that
all users share a 'public' namespace, thus providing behavior backwards
compatible with 7.2 and earlier releases. Probably the semantics and
default setting will need to be fine-tuned, but this is a start.
|
|
|
|
|
|
|
| |
2) Implement some options for SQLGetDescField().
3) Handle *Inifinity* timestamp for SQL_C_CHAR type output.
4) Separate Unicode conversions from common implementations.
5) Improve internal parse_statement() function.
|
|
|
|
|
|
|
|
| |
catalog namespace. This will not do as a production solution because
the interpretation of RI trigger arguments will vary depending on the
current namespace search path. I'm just putting it in so that the RI
regression tests don't fail while schema development proceeds. We
must find a better answer before 7.3 can be released.
|
|
|
|
|
| |
to rename. Avoids some corner-case bugs in cluster.c, improves
consistency with renameatt.
|
|
|
|
| |
temp table entries in pg_class have the names the user would expect.
|
|
|
|
|
|
| |
sequence functions how to cope with qualified names. Same code is
also used for int4notin, currtid_byrelname, pgstattuple. Also,
move TOAST tables into special pg_toast namespace.
|
| |
|
|
|
|
|
|
| |
in different namespaces. Also, cleanup work on relation namespace
support: drop, alter, rename commands work for tables in non-default
namespaces.
|
|
|
|
|
|
| |
calls with new or now-built-in versions. Make sure that all
calls to AC_DEFINE have a third argument, for possible use of
autoheader in the future.
|
|
|
|
| |
#ifdef NOT_USED).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
1) Prepare to separate 4 kinds of Descriptor handles.
2) Detect the transaction status more naturally.
3) Improve Parse Statement functionality for the use
of updatable cursors.
4) Improve updatable cursors.
5) Implement SQLGetDescField() and improve SQLColAttribute().
6) etc.
|
| |
|
|
|
|
|
| |
also fixed a NPE when calling the next() method on a result set after the
connection or resultset has been closed. (bug reported by Hans Deragon)
|
|
|
|
|
|
| |
in schemas other than the system namespace; however, there's no search
path yet, and not all operations work yet on tables outside the system
namespace.
|
|
|
|
| |
support
|
|
|
|
|
| |
Fixed NPE when database name was not passed on the jdbc connection URL
Fixed Connection.isClosed() to not hit the DB for every call
|
| |
|
| |
|
|
|
|
|
| |
- Use PyObject_Del() rather than macro version
- Check version and drop back to PyMem_Del() for older systems.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Also, fix debug logging of parse/plan trees so that the messages actually
go through elog(), not directly to stdout.
|
|
|
|
| |
there and CREATE SCHEMA will make entries in it...
|
| |
|
|
|
|
|
|
|
| |
addRangeTableEntry calls. Remove relname field from RTEs, since
it will no longer be a useful unique identifier of relations;
we want to encourage people to rely on the relation OID instead.
Further work on dumping qual expressions in EXPLAIN, too.
|
|
|
|
|
|
| |
objects to be privilege-checked. Some change in their APIs would be
necessary no matter what in the schema environment, and simply getting
rid of the name-based interface entirely seems like the best way.
|
| |
|
|
|
|
|
|
|
|
| |
the parsetree representation. As yet we don't *do* anything with schema
names, just drop 'em on the floor; but you can enter schema-compatible
command syntax, and there's even a primitive CREATE SCHEMA command.
No doc updates yet, except to note that you can now extract a field
from a function-returning-row's result with (foo(...)).fieldname.
|
|
|
|
| |
Report from Ryan Murray via Debian
|