| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
|
| | |
|
| |
|
|
| |
Per Alvaro.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
after the fact. Fix bug with incorrect test for whether we are at end
of logfile segment. Arrange for writes triggered by XLogInsert's
is-cache-more-than-half-full test to synchronize with the cache boundaries,
so that in long transactions we tend to write alternating halves of the
cache rather than randomly chosen portions of it; this saves one more
write syscall per cache load.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
erroring out as it has done for the last couple weeks. Document that this
form is now ignored because indexes can't usefully have different owners
from their parent tables. Fix pg_dump to not generate ALTER OWNER commands
for indexes.
|
| |
|
|
|
|
| |
discussion of getting around this by relaxing the checks made for regular
users, but I'm disinclined to toy with the security model right now,
so just special-case it for superusers where needed.
|
| |
|
|
| |
Also improve wording.
|
| |
|
|
|
|
|
|
|
| |
not accepting queries).
errmsg("database is not accepting queries to avoid
wraparound data loss in database \"%s\"",
errhint("Stop the postmaster and use a standalone
backend to VACUUM database \"%s\".",
|
| |
|
|
|
| |
chokes on IPv6 addresses, and comment out the IPv6 entry in the default
pg_hba.conf if so. Per Andrew Dunstan.
|
| |
|
|
|
| |
indexes all be int, rather than variously int, uint16 and uint32;
add some casts where necessary to support large buffer arrays.
|
| |
|
|
|
|
| |
in postgresql.conf.sample, mark custom_variable_classes as SIGHUP not
POSTMASTER to agree with the documentation (I can't see a reason it has
to be POSTMASTER so I think the docs are right).
|
| |
|
|
| |
> * Fix problems with wrong runtime encoding conversion for NLS message files
|
| |
|
|
| |
integer lists.
|
| |
|
|
|
|
|
|
|
|
|
| |
to 'Size' (that is, size_t), and install overflow detection checks in it.
This allows us to remove the former arbitrary restrictions on NBuffers
etc. It won't make any difference in a 32-bit machine, but in a 64-bit
machine you could theoretically have terabytes of shared buffers.
(How efficiently we could manage 'em remains to be seen.) Similarly,
num_temp_buffers, work_mem, and maintenance_work_mem can be set above
2Gb on a 64-bit machine. Original patch from Koichi Suzuki, additional
work by moi.
|
| |
|
|
|
| |
idea on consistency grounds, whether or not it really fixes bug #1831.
Michael Fuhr
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
insufficient paranoia in code that follows t_ctid links. (We must do both
because even with VACUUM doing it properly, the intermediate state with
a dangling t_ctid link is visible concurrently during lazy VACUUM, and
could be seen afterwards if either type of VACUUM crashes partway through.)
Also try to improve documentation about what's going on. Patch is a bit
bulky because passing the XMAX information around required changing the
APIs of some low-level heapam.c routines, but it's not conceptually very
complicated. Per trouble report from Teodor and subsequent analysis.
This needs to be back-patched, but I'll do that after 8.1 beta is out.
|
| | |
|
| |
|
|
| |
the right to stand out.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
or OFFSET clauses by using estimate_expression_value(). The main advantage
of this is that if the expression is a Param and we have a value for the
Param, we'll use that value rather than defaulting. Also, fix some
thinkos in the logic for combining LIMIT/OFFSET with an externally
supplied tuple fraction (this covers cases like EXISTS(...LIMIT...)).
And make sure the results of all this are shown by EXPLAIN. Per a
gripe from Merlin Moncure.
|
| |
|
|
| |
> o Remove unnecessary abstractions in pg_dump source code
|
| | |
|
| |
|
|
| |
> * -Prevent to_char() on interval from returning meaningless values
|
| |
|
|
|
|
|
|
| |
Fix to_char(interval) to return large year/month/day/hour values that
are larger than possible timestamp values.
Prevent to_char(interval) format specifications that make no sense, like
Month.
Clean up formatting.c code to more logically handle return lengths.
|
| |
|
|
|
| |
AbortTransaction. This can happen if a backend's InitPostgres transaction
fails (eg, because the given username is invalid). Per Alvaro.
|
| | |
|
| | |
|
| |
|
|
| |
integer with flags.
|
| | |
|
| | |
|
| |
|
|
| |
max_fsm_relations.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Run autoconf/autoheader in case someone forgot in the past.
|
| |
|
|
|
| |
anyway, and in assert-enabled builds you are likely to get an assertion
failure. Backpatch as far as 7.3; 7.2 seems not to have the problem.
|
| |
|
|
| |
and creation columns to behave for Unix or Win32.
|
| |
|
|
|
|
| |
caused PL languages and handlers to be dumped ALWAYS, even in the face
of contrary --schema or --table switches. Adopt a slightly saner
definition.
|
| |
|
|
| |
by forcing search_path to be just pg_catalog.
|
| |
|
|
|
|
|
|
|
| |
their OID parameter. It was possible to crash the backend with
select array_in('{123}',0,0); because that would bypass the needed step
of initializing the workspace. These seem to be the only two places
with a problem, though (record_in and record_recv don't have the issue,
and the other array functions aren't depending on user-supplied input).
Back-patch as far as 7.4; 7.3 does not have the bug.
|
| |
|
|
|
| |
working state, not fcinfo->context. Silly oversight on my part in last
go-round of fixes.
|
| |
|
|
|
|
|
|
| |
(the stats system has always collected this info, but the views were
filtering it out). Modify autovacuum so that over-threshold activity
in a toast table can trigger a VACUUM of the parent table, even if the
parent didn't appear to need vacuuming itself. Per discussion a month
or so back about "short, wide tables".
|
| | |
|
| |
|
|
| |
so that it will correctly dump owners of objects owned by non-login roles.
|
| | |
|
