| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
'make install'; there are enough of 'em that this slowed down the make
noticeably. Ensure that 'all' is the default make target in all these
directories (defaulting to 'make install' is surprising and dangerous
IMHO). Fix a couple small typos.
|
| |
|
|
|
|
|
| |
case for timestamptz input, and differently wrong answers in the float-
timestamp case for timestamp input.
|
|
|
|
|
|
|
| |
creation to world, but disallow temp table creation in template1. Per
latest round of pghackers discussion.
I did not force initdb, but the permissions lockdown on template1 will
not take effect unless you do one (or manually REVOKE TEMP ON DATABASE template1 FROM public).
|
|
|
|
| |
referring to "multibyte" where it really means character encoding.
|
|
|
|
|
|
|
| |
a series of localtime() calls to determine the local timezone offset
when mktime() fails. This eliminates regression failures on RHL 7.3,
and should continue to work until it occurs to the glibc boys to break
localtime() as well. By then I hope we'll have our own timezone code...
|
|
|
|
| |
convert date to tm' failures, by using DetermineLocalTimeZone() instead.
|
|
|
|
| |
(INT64_FORMAT), which gettext cannot handle.
|
|
|
|
| |
heap, not just ExclusiveLock.
|
| |
|
| |
|
|
|
|
|
| |
more flexible, and improve the error reporting. Also, add documentation
for REPLACE RULE/VIEW.
|
|
|
|
|
|
|
|
|
|
|
|
| |
> src/backend/optimizer/path/indxpath.c; see the "special indexable
> operators" stuff near the bottom of that file. (It's a bit of a crock
> that this code is hardwired there, and not somehow accessed through a
> system catalog, but it's what we've got at the moment.)
The attached patch re-enables a bytea right hand argument (as compared
to a text right hand argument), and enables index usage, for bytea LIKE
Joe Conway
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
already fixed by You. However there were a few left and attached patch
should fix the rest of them.
I used StringInfo only in 2 places and both of them are inside debug
ifdefs. Only performance penalty will come from using strlen() like all
the other code does.
I also modified some of the already patched parts by changing
snprintf(buf, 2 * BUFSIZE, ... style lines to
snprintf(buf, sizeof(buf), ... where buf is an array.
Jukka Holappa
|
|
|
|
|
|
| |
is an error, warning, etc.
Gavin Sherry
|
|
|
|
|
|
| |
pgmonitor.
Now log_min_error_statement uses it.
|
|
|
|
| |
because c.h has sys/types.h.
|
|
|
|
|
| |
Gavin Sherry, Neil Conway, and Tom Lane all got their hands dirty
on this one ...
|
|
|
|
|
|
|
|
|
|
| |
(overlaying low byte of page size) and add HEAP_HASOID bit to t_infomask,
per earlier discussion. Simplify scheme for overlaying fields in tuple
header (no need for cmax to live in more than one place). Don't try to
clear infomask status bits in tqual.c --- not safe to do it there. Don't
try to force output table of a SELECT INTO to have OIDs, either. Get rid
of unnecessarily complex three-state scheme for TupleDesc.tdhasoids, which
has already caused one recent failure. Improve documentation.
|
|
|
|
|
| |
Rename debug_print_query to log_statement and rename show_query_stats to
show_statement_stats.
|
|
|
|
| |
redundant pg_cast searches, fix obsolete comments.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
pointed out by Barry Lind: UPDATE bigintcol = 10000000000 fails because
the constant is initially taken as float8. We really need a better way,
but it's not gonna happen for 7.3.
Also, remove int4reltime() function, which is redundant with the
existing binary-compatibility coercion path from int4 to reltime,
and probably has been unreachable code for a long while.
|
|
|
|
|
|
|
|
|
| |
type for runtime constraint checks, instead of misusing the parse-time
Constraint node for the purpose. Fix some damage introduced into type
coercion logic; in particular ensure that a coerced expression tree will
read out the correct result type when inspected (patch had broken some
RelabelType cases). Enforce domain NOT NULL constraints against columns
that are omitted from an INSERT.
|
| |
|
|
|
|
|
|
| |
you try to use the tupdesc to build a tuple.
Joe Conway
|
|
|
|
|
|
|
|
| |
available (else there's no way to interpret the list links). Change
pg_locks view to show transaction ID locks separately from ordinary
relation locks. Avoid showing N duplicate rows when the same lock is
held multiple times (seems unlikely that users care about exact hold
count). Improve documentation.
|
|
|
|
|
|
| |
functions, per suggestion from John Gray and Joe Conway. Also, fix
plpgsql RETURN NEXT to verify that returned values match the expected
tupdesc.
|
|
|
|
|
|
|
|
|
| |
to false provides more SQL-spec-compliant behavior than we had before.
I am not sure that setting it false is actually a good idea yet; there
is a lot of client-side code that will probably be broken by turning
autocommit off. But it's a start.
Loosely based on a patch by David Van Wie.
|
| |
|
|
|
|
|
|
| |
column additions, deletions, and renames that would let a child table
get out of sync with its parent. Patch by Alvaro Herrera, with some
kibitzing by Tom Lane.
|
|
|
|
|
| |
* Remove wal_files postgresql.conf option because WAL files are
now recycled
|
|
|
|
| |
Improve wording of pre-7.3 syntax mention.
|
|
|
|
| |
which is now required.
|
|
|
|
|
| |
that the functionality is available to anyone via ReturnSetInfo, rather
than hard-wiring it to PL/pgSQL.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
> Upon invoking a polygon(integer, circle) function a
> src/backend/utils/adt/geo_ops.c:circle_poly() function will gets
> called, which suffers from a buffer overflow.
>
> 2) A src/backend/adt/utils/geo_ops.c:path_encode() fails to detect a
> buffer overrun condition. It is called in multiple places, the most
> interesting are path_out() and poly_out() functions.
> 5) A src/backend/utils/adt/geo_ops.c:path_add() also fails to detect
> a simple buffer overrun.
I've attached a patch which should fix these problems.
Neil Conway
|
|
|
|
|
|
| |
memory.
Neil Conway
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
connections by the superuser only.
This patch replaces the last patch I sent a couple of days ago.
It closes a connection that has not been authorised by a superuser if it would
leave less than the GUC variable ReservedBackends
(superuser_reserved_connections in postgres.conf) backend process slots free
in the SISeg. This differs to the first patch which only reserved the last
ReservedBackends slots in the procState array. This has made the free slot
test more expensive due to the use of a lock.
After thinking about a comment on the first patch I've also made it a fatal
error if the number of reserved slots is not less than the maximum number of
connections.
Nigel J. Andrews
|
|
|
|
|
|
|
| |
to the table function, thus preventing memory leakage accumulation across
calls. This means that SRFs need to be careful to distinguish permanent
and local storage; adjust code and documentation accordingly. Patch by
Joe Conway, very minor tweaks by Tom Lane.
|
|
|
|
| |
Per pghackers discussion from back around 1-August.
|
|
|
|
|
| |
tables that need special defenses. I believe this is okay even for
TOAST tables that belong to system tables.
|
| |
|
|
|
|
| |
pghackers discussion around 31-Jul-02.
|
|
|
|
|
|
| |
ERROR: Cannot display a value of type RECORD
rather than a random integer when someone tries to SELECT a tuple
value. Per pghackers discussion around 26-May-02.
|
|
|
|
| |
This breaks support for 6.2 or older client libraries.
|
|
|
|
| |
defined in the FROM clause. From Joe Conway, with some tweaks.
|
|
|
|
|
| |
types, SRFs. Not happy with memory management yet, but I'll commit these
other changes.
|
| |
|
| |
|