- 22 11月, 2005 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Teodor Sigaev 提交于
-
- 21 11月, 2005 5 次提交
-
-
由 Alvaro Herrera 提交于
process of dropping roles by dropping objects owned by them and privileges granted to them, or giving the owned objects to someone else, through the use of the data stored in the new pg_shdepend catalog. Some refactoring of the GRANT/REVOKE code was needed, as well as ALTER OWNER code. Further cleanup of code duplication in the GRANT code seems necessary. Implemented by me after an idea from Tom Lane, who also provided various kind of implementation advice. Regression tests pass. Some tests for the new functionality are also added, as well as rudimentary documentation.
-
由 Teodor Sigaev 提交于
- supports multibyte encodings - more strict rules for lexemes - flex isn't used Add: - tsquery plainto_tsquery(text) Function makes tsquery from plain text. - &&, ||, !! operation for tsquery for combining tsquery from it's parts: 'foo & bar' || 'asd' => 'foo & bar | asd'
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
the convenience of tuptoaster.c and is no longer needed, so may as well get rid of some small amount of overhead.
-
由 Tom Lane 提交于
tuple in-place, but instead passes back an all-new tuple structure if any changes are needed. This is a much cleaner and more robust solution for the bug discovered by Alexey Beschiokov; accordingly, revert the quick hack I installed yesterday. With this change, HeapTupleData.t_datamcxt is no longer needed; will remove it in a separate commit in HEAD only.
-
- 20 11月, 2005 3 次提交
-
-
由 Tom Lane 提交于
doing heap_insert or heap_update, wipe out any extracted fields in the TupleTableSlot containing the tuple, because they might not be valid anymore if tuptoaster.c changed the tuple. Safe because slot must be in the materialized state, but mighty ugly --- find a better answer!
-
由 Tom Lane 提交于
not only the array contents, before claiming two arrays are equal. Per recent discussion.
-
由 Andrew Dunstan 提交于
DROP objecttype IF EXISTS for the following objects: table view index sequence schema type domain conversion
-
- 19 11月, 2005 6 次提交
-
-
由 Tom Lane 提交于
more tests than strictly necessary, but did not feel like tracing call paths in detail ...
-
由 Tom Lane 提交于
be useful to actually do something with nulls, rather than reject them, but I'll just close the hole for now.
-
由 Tom Lane 提交于
the array (for array_push) or higher-dimensional array (for array_cat) rather than decrementing it as before. This avoids generating lower bounds other than one for any array operation within the SQL spec. Per recent discussion. Interestingly, this seems to have been the original behavior, because while updating the docs I noticed that a large fraction of relevant examples were *wrong* for the old behavior and are now right. Is it worth correcting this in the back-branch docs?
-
由 Tom Lane 提交于
recursed twice on its first argument, leading to exponential time spent on a deep nest of COALESCEs ... such as a deeply nested FULL JOIN would produce. Per report from Matt Carter.
-
由 Andrew Dunstan 提交于
translate undef to NULL for result arrayref, now that we allow NULLs in arrays. Update plperl regression test accordingly.
-
由 Alvaro Herrera 提交于
-
- 18 11月, 2005 6 次提交
-
-
由 Neil Conway 提交于
-
由 Tom Lane 提交于
contents directly.
-
由 Bruce Momjian 提交于
J.Kuwamura
-
由 Andrew Dunstan 提交于
make psql honor explicit database parameter in -l mode, in case "postgres" database is missing - per complaint from Philip Yarra.
-
由 Tom Lane 提交于
functionality, but I still need to make another pass looking at places that incidentally use arrays (such as ACL manipulation) to make sure they are null-safe. Contrib needs work too. I have not changed the behaviors that are still under discussion about array comparison and what to do with lower bounds.
-
由 Tom Lane 提交于
that was added to localbuf.c in 8.1; therefore, applying it to a temp table left corrupt lookup state in memory. The only case where this had a significant chance of causing problems was an ON COMMIT DELETE ROWS temp table; the other possible paths left bogus state that was unlikely to be used again. Per report from Csaba Nagy.
-
- 17 11月, 2005 3 次提交
-
-
由 Bruce Momjian 提交于
< so duplicate checking can be easily performed. > so duplicate checking can be easily performed. It is possible to > do it without a unique index if we require the user to LOCK the table > before the MERGE.
-
由 Tom Lane 提交于
its result when the clause was an OR clause. Brain fade exposed by example from Sebastian BÎck.
-
由 Bruce Momjian 提交于
< * Add a libpq function to support Parse/DescribeStatement capability < * Add PQescapeIdentifier() to libpq < * Prevent PQfnumber() from lowercasing unquoted the column name < < PQfnumber() should never have been doing lowercasing, but historically < it has so we need a way to prevent it < 648a642,661 > > > libpq > > o Add a function to support Parse/DescribeStatement capability > o Add PQescapeIdentifier() > o Prevent PQfnumber() from lowercasing unquoted the column name > > PQfnumber() should never have been doing lowercasing, but > historically it has so we need a way to prevent it > > o Allow query results to be automatically batched to the client > > Currently, all query results are transfered to the libpq > client before libpq makes the results available to the > application. This feature would allow the application to make > use of the first result rows while the rest are transfered, or > held on the server waiting for them to be requested by libpq. > One complexity is that a query like SELECT 1/col could error > out mid-way through the result set.
-
- 16 11月, 2005 6 次提交
-
-
由 Tatsuo Ishii 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> > To implement this cleanly requires that the table have a unique index > so duplicate checking can be easily performed. >
-
由 Bruce Momjian 提交于
features.
-
- 15 11月, 2005 7 次提交
-
-
由 Bruce Momjian 提交于
names from being added to pgindent's typedef list. The existance of them caused weird formatting in the date/type files, and in keywords.c. Backpatch to 8.1.X.
-
由 Bruce Momjian 提交于
columns, shifting comment to the right when more than 150 'else if' clauses were used, and update typedefs for 8.1.X. NetBSD patched updated, with documentation.
-
由 Tom Lane 提交于
sense and rename to "outerjoin_delayed" to more clearly reflect what it means). I had decided that it was redundant in 8.1, but the folly of this is exposed by a bug report from Sebastian Böck. The place where it's needed is to prevent orindxpath.c from cherry-picking arms of an outer-join OR clause to form a relation restriction that isn't actually legal to push down to the relation scan level. There may be some legal cases that this forbids optimizing, but we'd need much closer analysis to determine it.
-
由 Alvaro Herrera 提交于
-
由 Bruce Momjian 提交于
Cosmetic fix only.
-
由 Tom Lane 提交于
slot of the topmost plan node when a trigger returns a modified tuple. These appear to be the only places where a plan node's caller did not treat the result slot as read-only, which is an assumption that nodeUnique makes as of 8.1. Fixes trigger-vs-DISTINCT bug reported by Frank van Vugt.
-
由 Teodor Sigaev 提交于
of self-defined macros, add limit of Array to gist__int_ops. BTW, intarray now doesn't support NULLs in arrays.
-
- 14 11月, 2005 2 次提交
-
-
由 Teodor Sigaev 提交于
Use postgres-wide macros BITS_PER_BYTE instead self-definenig macros, also use it for calculating bit length of TPQTGist
-
由 Teodor Sigaev 提交于
-