| Age | Commit message (Collapse) | Author |
|---|
|
transaction, unless rolled back or overridden by a SET clause for the same
variable attached to a surrounding function call. Per discussion, these
seem the best semantics. Note that this is an INCOMPATIBLE CHANGE: in 8.0
through 8.2, SET LOCAL's effects disappeared at subtransaction commit
(leading to behavior that made little sense at the SQL level).
I took advantage of the opportunity to rewrite and simplify the GUC variable
save/restore logic a little bit. The old idea of a "tentative" value is gone;
it was a hangover from before we had a stack. Also, we no longer need a stack
entry for every nesting level, but only for those in which a variable's value
actually changed.
|
|
|
|
Fix grammatical errors in its description.
|
|
> http://archives.postgresql.org/pgsql-hackers/2007-09/msg00051.php
|
|
databases, per gripe from hubert depesz lubaczewski. Patch from
Simon Riggs.
|
|
< * Reduce XID consumption of read-only queries
<
< http://archives.postgresql.org/pgsql-hackers/2007-08/msg00516.php
<
<
> * -Reduce XID consumption of read-only queries
|
|
rows will normally never obtain an XID at all. We already did things this way
for subtransactions, but this patch extends the concept to top-level
transactions. In applications where there are lots of short read-only
transactions, this should improve performance noticeably; not so much from
removal of the actual XID-assignments, as from reduction of overhead that's
driven by the rate of XID consumption. We add a concept of a "virtual
transaction ID" so that active transactions can be uniquely identified even
if they don't have a regular XID. This is a much lighter-weight concept:
uniqueness of VXIDs is only guaranteed over the short term, and no on-disk
record is made about them.
Florian Pflug, with some editorialization by Tom.
|
|
Random other wordsmithing.
|
|
(Actually, it works as a plain statement too, but I didn't document that
because it seems a bit useless.) Unify VariableResetStmt with
VariableSetStmt, and clean up some ancient cruft in the representation of
same.
|
|
There are still some loose ends: I didn't do anything about the SET FROM
CURRENT idea yet, and it's not real clear whether we are happy with the
interaction of SET LOCAL with function-local settings. The documentation
is a bit spartan, too.
|
|
|
|
|
|
|
|
Some alignment cleanups.
|
|
|
|
tool chains).
|
|
"index" entries for GIN/GiST.
|
|
|
|
entire section, per Peter.
|
|
entries in textsearch.sgml.
|
|
older SGML toolchains.
|
|
|
|
|
|
|
|
to be more logical.
|
|
the main documentation, out of its own text search chapter.
|
|
|
|
section makes a little more sense.
|
|
|
|
|
|
|
|
|
|
|
|
fixes. Not sure how these weren't comitted before.
|
|
but just hardwire the specified timezone database path into the executable.
Per discussion, this avoids some packaging disadvantages of using a
symlink.
|
|
minor rewording, some markup fixups. Lots left to do here ...
|
|
|
|
Transactional Information Systems by Gerhard Weikum, Kaufmann
|
|
|
|
This prevents needing to do complex and poorly-defined updates of the
mapping table if the new parser has different token types than the old.
Per discussion.
|
|
syncing the existing docs with the final syntax decisions.
|
|
init options of the template as top-level options in the syntax. This also
makes ALTER a bit easier to use, since options can be replaced individually.
I also made these statements verify that the tmplinit method will accept
the new settings before they get stored; in the original coding you didn't
find out about mistakes until the dictionary got invoked.
Under the hood, init methods now get options as a List of DefElem instead
of a raw text string --- that lets tsearch use existing options-pushing code
instead of duplicating functionality.
|
|
pages for the new SQL commands. I also committed Bruce's text search
introductory chapter, as-is except for fixing some markup errors,
so that there would be a place for the reference pages to link to.
|
|
|
|
Oleg Bartunov and Teodor Sigaev, but I did a lot of editorializing,
so anything that's broken is probably my fault.
Documentation is nonexistent as yet, but let's land the patch so we can
get some portability testing done.
|
|
database.
|
|
|
|
< * Allow server log information to be output as INSERT statements
> * -Allow server log information to be output as CSV format
|
|
redirect_stderr to logging_collector.
Original patch from Arul Shaji, subsequently modified by Greg Smith, and then
heavily modified by me.
|
|
>
> * Reduce XID consumption of read-only queries
>
> http://archives.postgresql.org/pgsql-hackers/2007-08/msg00516.php
>
|
