| Age | Commit message (Collapse) | Author |
|---|
|
|
|
simplify the syntax examples by unifying user and group cases, and fix
no-longer-correct example of psql \z output. Per Erwin Brandstetter.
|
|
LEAST handle NULL arguments differently than we do. Per a discussion
on 30-Jun that somehow didn't get done.
|
|
Guillaume Lelarge
|
|
corochoone@gmail.com
|
|
|
|
excerpts of a document. That's clearly desirable, but the functionality
is not there yet.
|
|
per recommendation from Alvaro. This doesn't force initdb since the
numeric token type in the catalogs doesn't change; but note that
the expected regression test output changed.
|
|
hyphenated-word parser examples per earlier discussion with Alvaro.
|
|
|
|
cases.
|
|
Jun Kuwamura
|
|
Ulrich Kroener
|
|
the sequence. Also, make setval() with is_called = false not affect the
currval state, either. Per report from Kris Jurka that an implicit
ALTER SEQUENCE OWNED BY unexpectedly caused currval() to become valid.
Since this isn't 100% backwards compatible, it will go into HEAD only;
I'll put a more limited patch into 8.2.
|
|
|
|
|
|
in corner cases such as re-fetching a just-deleted row. We may be able to
relax this someday, but let's find out how many people really care before
we invest a lot of work in it. Per report from Heikki and subsequent
discussion.
While in the neighborhood, make the combination of INSENSITIVE and FOR UPDATE
throw an error, since they are semantically incompatible. (Up to now we've
accepted but just ignored the INSENSITIVE option of DECLARE CURSOR.)
|
|
|
|
if there are zero rows to aggregate over, and the API seems both conceptually
and notationally ugly anyway. We should look for something that improves
on the tsquery-and-text-SELECT version (which is also pretty ugly but at
least it works...), but it seems that will take query infrastructure that
doesn't exist today. (Hm, I wonder if there's anything in or near SQL2003
window functions that would help?) Per discussion.
|
|
categories, as per discussion. asciiword (formerly lword) is still
ASCII-letters-only, and numword (formerly word) is still the most general
mixed-alpha-and-digits case. But word (formerly nlword) is now
any-group-of-letters-with-at-least-one-non-ASCII, rather than all-non-ASCII as
before. This is no worse than before for parsing mixed Russian/English text,
which seems to have been the design center for the original coding; and it
should simplify matters for parsing most European languages. In particular
it will not be necessary for any language to accept strings containing digits
as being regular "words". The hyphenated-word categories are adjusted
similarly.
|
|
James Shaw. Also update a couple of examples to reflect 8.3's improved
plan-printing code.
|
|
active dictionary and its output lexemes as separate columns, instead
of smashing them into one text column, and lowercase the column names.
Also, define the output rowtype using OUT parameters instead of a
composite type, to be consistent with the other built-in functions.
|
|
users of tsearch. This isn't meant to be permanent documentation,
but to call out the areas that need either fixing or real documentation.
|
|
more clearly, improve a lot of unclear descriptions, add some missing
material. We still need a migration guide though.
|
|
Jun Kuwamura
|
|
|
|
|
|
|
|
Ian Barwick
|
|
the syslog configuration file (at least not on most known Unixen).
I dunno why we hadn't had that info in the docs all along ...
|
|
|
|
|
|
|
|
|
|
8.3 consistently.
|
|
|
|
|
|
entries and removed a few.
|
|
<H3 id="item4.19">4.19) Why do I get "relation with OID #####
does not exist" errors when accessing temporary tables in PL/PgSQL
functions?</H3>
|
|
Notably, standardize on using "token" for the strings output by a parser,
while "lexeme" is reserved for the normalized strings produced by a
dictionary.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
these are more easily and usefully maintained as contrib modules.
Various other wordsmithing, markup improvement, etc.
|
|
for Slony and Skytools to depend on it. Per discussion.
|
|
the "relation with OID ##### does not exist" item, and some URL
corrections.
Ian Barwick
|
|
|
