| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
| |
data, and both have filled the transmission buffers. One scenario where
this can happen was illustrated here:
http://archives.postgresql.org/pgsql-hackers/2003-04/msg00979.php
|
| |
|
|
|
|
|
| |
machine readable, without headers, not sorted. Parameter descriptions
adjusted to fit first sentence + rest convention.
|
|
|
|
|
|
|
|
|
|
| |
fully search-path-proof yet; also, element_types view did not work for
parameters and result types of functions, because it didn't generate
the object_name for the function the same way the data_type_privileges
view does. While at it, centralize dependencies on INDEX_MAX_KEYS/
FUNC_MAX_ARGS into a function returning setof int, so that it will be
easier to fix information_schema for nonstandard values of these
parameters.
|
|
|
|
|
| |
I inadvertently broke a few days ago (per report from Sean Thomas).
Add regression test case to try to catch any similar breakage in future.
|
| |
|
|
|
|
|
|
|
|
| |
Use pg_get_constraintdef instead of pg_constraint.consrc
Use UNION ALL instread of UNION
Make use of regclass type for getting OID of system catalogs
Add schema qualifications where necessary
Fix typos
|
|
|
|
| |
well spotted by Neil Conway.
|
| |
|
| |
|
|
|
|
|
| |
digits, and label it 'ms' not 'msec', for consistency with psql's \timing
display. Per recent discussions.
|
|
|
|
|
| |
a portion of a patch recently submitted by Christopher Kings-Lynne.
Applied by agreement that this is a bug fix.
|
| |
|
|
|
|
| |
tab-completing.
|
|
|
|
|
|
|
|
|
|
|
| |
of the entries used to be zero, which I think I had deliberately done in
the name of saving cycles during ANALYZE, but it was really a rather
foolish decision. Some of the more complex views in information_schema
were getting really bad plans for lack of statistics on the columns they
were joining over.
I'm not forcing an initdb for this, but I think there will be one soon
anyway to repair some bugs in the information_schema views.
|
| |
|
|
|
|
|
|
|
|
| |
memory say 'out of shared memory'; some were doing that and some just
said 'out of memory'. Also add a HINT about increasing max_locks_per_transaction
where relevant, per suggestion from Sean Chittenden. (The former change
does not break the strings freeze; the latter does, but I think it's
worth doing anyway.)
|
|
|
|
|
| |
identifiers --- it will now complete these correctly with double quoting.
Fix a few other issues in passing.
|
|
|
|
|
|
|
|
|
|
| |
protocol, per report from Igor Shevchenko. NOTIFY thought it could
do its thing if transaction blockState is TBLOCK_DEFAULT, but in
reality it had better check the low-level transaction state is
TRANS_DEFAULT as well. Formerly it was not possible to wait for the
client in a state where the first is true and the second is not ...
but now we can have such a state. Minor cleanup in StartTransaction()
as well.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
up by quotes or backslashes in words that are being matched to database
names (per gripe from Ian Barwick, though I didn't use his patch).
Also fix possible memory leakage if _complete_with_query isn't run to
completion (not clear if that can happen or not, but be safe).
|
| |
|
|
|
|
|
| |
it. Not sure why I'd thought it would be a good idea to do differently
way back when, but Greg Stark exposed the folly of doing so ...
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
be made, to avoid corner cases where max_connections ends up unreasonably
small because shared_buffers is hogging too much shmem space. Per pghackers
discussion about a week ago. Also, fix the copy-newlines problem in a
more robust way, by using COPY FROM filename instead of COPY FROM STDIN;
per a suggestion from Peter.
|
|
|
|
|
|
|
|
|
| |
when the pg_class.relhassubclass value is already correct. This should
avoid most cases of the 'tuple concurrently updated' problem that
Robert Creager recently complained about. Also remove a bunch of dead
code in StoreCatalogInheritance() --- it was still computing the complete
list of direct and indirect inheritance ancestors, though that list has
not been needed since we got rid of the pg_ipl catalog.
|
|
|
|
|
|
| |
rather than allocating them on the stack.
Fixes complaint from gcc 3.3.1.
|
| |
|
| |
|
|
|
|
| |
already check for alignment.
|
| |
|
| |
|
|
|
|
|
|
|
| |
when -fstrict-aliasing is turned on, as it is in the latest gcc when you
use -O2
Andrew Dunstan
|
| |
|
| |
|
|
|
|
| |
Manfred Koizar
|
| |
|
|
|
|
| |
Andrew Dunstan
|
| |
|
|
|
|
|
|
|
|
| |
misscanning of this construct:
SELECT ''hello world''
-- SELECT ''goodbye world''
::text;
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|