| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
| |
syntax for language names (instead of 'string').
createlang now handles the case where a second language uses the same call
handler as an already installed language (e.g., plperl/plperlu).
droplang now handles the reverse case, i.e., dropping a language where
the call handler is still used by another language. Moreover, droplang
can now be used to drop any user-defined language, not just the supplied
ones.
|
| |
|
|
|
|
| |
From Joe Conway.
|
| |
|
|
|
|
| |
Needed to keep pg_dump from getting confused.
|
|
|
|
|
|
| |
Don't hardcode the maximum accepted server version, use PG_VERSION instead.
Install a notice processor so notices are handled like error messages.
Word smithing.
|
| |
|
|
|
|
| |
case where there are resjunk columns in the query.
|
|
|
|
| |
awhile, but the man page didn't know it.
|
| |
|
|
|
|
| |
Other small improvements.
|
|
|
|
| |
our own code ...
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
default, but OIDS are removed from many system catalogs that don't need them.
Some interesting side effects: TOAST pointers are 20 bytes not 32 now;
pg_description has a three-column key instead of one.
Bugs fixed in passing: BINARY cursors work again; pg_class.relhaspkey
has some usefulness; pg_dump dumps comments on indexes, rules, and
triggers in a valid order.
initdb forced.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
appears to be duplicated (two identical <listitems> right after each
other). Here is a quick patch to remove one instance of it.
Magnus Hagander
|
|
|
|
|
|
|
|
|
|
|
| |
* Merges identical code from org.postgresql.jdbc[1|2].Statement into
org.postgresql.Statement.
* Moves escapeSQL() method from Connection to Statement (the only place
it's used)
* Minor cleanup of the new isolation level stuff.
* Minor cleanup of version string handling.
Anders Bengtsson
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(as proposed in http://fts.postgresql.org/db/mw/msg.html?mid=1028327)
2. support for 'pass-by-value' arguments - to test this
we used special opclass for int4 with values in range [0-2^15]
More testing will be done after resolving problem with
index_formtuple and implementation of B-tree using GiST
3. small patch to contrib modules (seg,cube,rtree_gist,intarray) -
mark functions as 'isstrict' where needed.
Oleg Bartunov
|
|
|
|
| |
Neil Padgett
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
consistent type naming.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
be able to apply against what you just committed. It rolls soundex into
fuzzystrmatch.
Remove soundex/metaphone and merge into fuzzystrmatch.
Joe Conway
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here is a context diff from latest cvs
And I see why you couldn't apply the last diff, the setCatalog diff has
been backed out, that was causing the compile problem in the first
place.
This following one needs to be applied to allow the current cvs to
compile
Dave Cramer
|
|
|
|
| |
Cyril VELTER
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
metaphone() in a contrib. There seem to be a fair number of different
approaches to both of these algorithms. I used the simplest case for
levenshtein which has a cost of 1 for any character insertion, deletion, or
substitution. For metaphone, I adapted the same code from CPAN that the PHP
folks did.
A couple of questions:
1. Does it make sense to fold the soundex contrib together with this one?
2. I was debating trying to add multibyte support to levenshtein (it would
make no sense at all for metaphone), but a quick search through the contrib
directory found no hits on the word MULTIBYTE. Should worry about adding
multibyte support to levenshtein()?
Joe Conway
|
| |
|
| |
|
| |
|
|
|
|
| |
response, to avoid noise in the server log.
|
|
|
|
|
| |
since it's completely redundant with regress.sgml. I think we agreed to
remove it awhile back, actually, but no one got around to doing it.
|
|
|
|
| |
files.
|
|
|
|
| |
Add some resultmap entries for SCO OpenServer.
|
|
|
|
| |
error message.
|
|
|
|
|
|
| |
clauses are equal(), before trying to match them up using btree opclass
inference rules. This allows it to recognize many simple cases involving
non-btree operations, for example 'x IS NULL'. Clean up code a little.
|
|
|
|
| |
ExecEvalExpr, to avoid possible memory leak.
|
|
|
|
| |
install prefix=elsewhere' works.
|