| Age | Commit message (Collapse) | Author |
|---|
|
Martijn van Oosterhout
|
|
demonstrating that its intent wasn't obvious.
|
|
Martijn van Oosterhout
|
|
---------------------------------------------------------------------------
Add dynamic record inspection to PL/PgSQL, useful for generic triggers:
tval2 := r.(cname);
or
columns := r.(*);
Titus von Boxberg
|
|
into HEAD.
|
|
Simon Riggs
|
|
|
|
Qingqing Zhou
|
|
versions of OpenSSL. If your OpenSSL does not contain SHA2, then there
should be no conflict. But ofcourse, if someone upgrades OpenSSL,
server starts crashing.
Backpatched to 8.1.X.
Marko Kreen
|
|
#define inline __inline
Backpatch to 8.1.X.
Hiroshi Saito
|
|
|
|
Dave Page
|
|
tval2 := r.(cname);
or
columns := r.(*);
Titus von Boxberg
|
|
|
|
Joachim Wieland
|
|
An article at WebProNews quoted from the PG docs as to the merits of
stored procedures. I have added a bit more material on their merits,
as well as making a few changes to improve the introductions to
PL/Perl and PL/Tcl.
Chris Browne
|
|
J.Kuwamura
|
|
> * Consider GnuTLS if OpenSSL license becomes a problem
>
> See http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php.
|
|
|
|
---------------------------------------------------------------------------
Delay write of pg_stats file to once every five minutes, during
shutdown, or when requested by a backend:
It changes so the file is only written once every 5 minutes (changeable
of course, I just picked something) instead of once every half second.
It's still written when the stats collector shuts down, just as before.
And it is now also written on backend request. A backend requests a
rewrite by simply sending a special stats message. It operates on the
assumption that the backends aren't actually going to read the
statistics file very often, compared to how frequent it's written today.
Magnus Hagander
|
|
> o Allow timezone names in SQL strings, '2006-05-24 21:11
> Americas/New_York'::timestamptz
|
|
|
|
with a fresh local value for each invocation, to avoid unexpected sharing
violations. Per recent -hackers discussion.
|
|
If user picksplit on n-th column generate equals
left and right unions then it calls picksplit on n+1-th
column.
|
|
From Andreas Seltenreich <[email protected]>
|
|
wasn't exported by exports.txt. Ooops. Per buildfarm results.
|
|
and standard_conforming_strings; likewise for the other client programs
that need it. As per previous discussion, a pg_dump dump now conforms
to the standard_conforming_strings setting of the source database.
We don't use E'' syntax in the dump, thereby improving portability of
the SQL. I added a SET escape_strings_warning = off command to keep
the dumps from getting a lot of back-chatter from that.
|
|
Per Coverity bug #304. Thanks to Martijn van Oosterhout for reporting it.
Zero out the pointer fields of PGresult so that these mistakes are more
easily catched, per discussion.
|
|
|
|
|
|
in place though, so that it plays nicely with older servers.
Per discussion.
|
|
|
|
current setting of standard_conforming_strings to decide how to quote
strings that will be used later. There is much more to do here but
this particular change breaks the build on Windows, so fix it now.
|
|
superuser password, and also in the paths of the various files it issues
SQL COPY commands for. Per bug #2424.
|
|
JOIN, which I removed in a recent fit of over-optimism that we wouldn't
have any future use for it. Now it's needed to support disambiguating
WITH CHECK OPTION from WITH TIME ZONE. As proof of concept, add stub
grammar productions for WITH CHECK OPTION.
|
|
this works.
|
|
'off'. This allows pg_dump output with standard_conforming_strings =
'on' to generate proper strings that can be loaded into other databases
without the backslash doubling we typically do. I have added the
dumping of the standard_conforming_strings value to pg_dump.
I also added standard backslash handling for plpgsql.
|
|
per-call overhead is quite significant, at least on Linux: whatever
it's doing is more than just shoving the bytes into a buffer. Buffering
the data so we can call fwrite() just once per row seems to be a win.
|
|
during COPY OUT. Andreas Pflug, some editorialization by moi.
|
|
Chris Browne
|
|
regression test.
|
|
kept but now deprecated. Patch from Adam Sjøgren. Add regression test to
show plperl trigger data (Andrew).
TBD: apply similar changes to plpgsql, plpython and pltcl.
|
|
By Andreas Seltenreich <[email protected]>
|
|
CopySendData.
|
|
really tables and shouldn't get DISABLE TRIGGER processing. Per bug
#2452 from Robert Treat.
|
|
< pg_attribute.attislocal has to be set to 'false' for ADD, and
< pg_attribute.attinhcount adjusted appropriately
> See http://archives.postgresql.org/pgsql-hackers/2006-05/msg00988.php.
|
|
* some refactoring and simplify code int gistutil.c and gist.c
* now in some cases it can be called used-defined
picksplit method for non-first column in index, but here
is a place to do more.
* small fix of docs related to support NULL.
|
|
|
|
the thread-safety status of the library.
|
|
and transaction visibility fields of tuples being sorted. These are
always uninteresting in a tuple being sorted (if the fields were actually
selected, they'd have been pulled out into user columns beforehand).
This saves about 24 bytes per row being sorted, which is a useful savings
for any but the widest of sort rows. Per recent discussion.
|
