| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
| |
Needed to accommodate different layout on some platforms (Debian for
one). Heikki Linnakangas
|
|
|
|
| |
ITAGAKI Takahiro
|
|
|
|
| |
Per Greg Stark & Dave Page
|
|
|
|
|
| |
into SHAREDIR/tsearch_data. Use this instead of ad-hoc coding in
dict_xsyn/Makefile. Should fix current ContribCheck failures on MSVC.
|
|
|
|
|
| |
hard-to-maintain textual examples currently in the SGML docs. From
Sergey Karpov.
|
| |
|
|
|
|
|
| |
on SerializableSnapshot, minor other cleanup. Marko Kreen, some further
editorialization by me.
|
| |
|
|
|
|
| |
Some additional minor editorializing by Tom.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on CORE previously.
This module offers transaction ID's containing the original XID and the
transaction epoch as a bigint value to the user level. It also provides
a special txid_snapshot data type that contains an entire transactions
visibility snapshot information, which is useful to determine if a
particular txid was visible to a transaction or not.
The module has been tested by porting Slony-I from using its original
xxid data type.
Jan
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
testing). Combine the formerly independent opclasses for the various
ISN types into opfamilies. The latter causes some extra bleating from
opr_sanity, since the module doesn't provide complete sets of cross-type
operators, but it's still a good idea because it will give the planner
more information to work with. The missing cross-type operators no longer
pose a risk of unexpected planner errors in 8.3, so there's no need to
insist on filling them in (and I gather it wouldn't be very sound
semantically to add them all).
|
|
|
|
| |
Found by running opr_sanity on contrib modules.
|
|
|
|
| |
Found by running opr_sanity on contrib modules.
|
|
|
|
| |
Found by running opr_sanity on contrib modules.
|
|
|
|
| |
Found by running opr_sanity on contrib modules.
|
|
|
|
| |
Found by running opr_sanity on contrib modules.
|
|
|
|
|
| |
any commutator operator for =(chkpass,text), so this was creating a
shell operator that would fail on use. Found by opr_sanity testing.
|
|
|
|
| |
Found by running opr_sanity on contrib modules.
|
|
|
|
| |
which is the case at least on some Solaris versions. Marko Kreen
|
|
|
|
|
|
|
| |
couldn't possibly HAVE_GETOPT. I believe this is the most appropriate
form of the patch submitted 2007-08-07 by Hiroshi Saito, though not
having a Windows build environment I won't know for sure till I see
the buildfarm results.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- create a separate archive_mode GUC, on which archive_command is dependent
- %r option in recovery.conf sends last restartpoint to recovery command
- %r used in pg_standby, updated README
- minor other code cleanup in pg_standby
- doc on Warm Standby now mentions pg_standby and %r
- log_restartpoints recovery option emits LOG message at each restartpoint
- end of recovery now displays last transaction end time, as requested
by Warren Little; also shown at each restartpoint
- restart archiver if needed to carry away WAL files at shutdown
Simon Riggs
|
|
|
|
|
|
| |
unpruned XMAX in its header. At the cost of 4 bytes per page, this keeps us
from performing heap_page_prune when there's no chance of pruning anything.
Seems to be necessary per Heikki's preliminary performance testing.
|
|
|
|
|
|
|
|
|
|
|
|
| |
columns, and the new version can be stored on the same heap page, we no longer
generate extra index entries for the new version. Instead, index searches
follow the HOT-chain links to ensure they find the correct tuple version.
In addition, this patch introduces the ability to "prune" dead tuples on a
per-page basis, without having to do a complete VACUUM pass to recover space.
VACUUM is still needed to clean up dead index entries, however.
Pavan Deolasee, with help from a bunch of other people.
|
|
|
|
|
| |
contrib/intarray's GIN opclass override the built-in default. Per bug #3048
and other complaints.
|
|
|
|
|
|
|
|
|
| |
than two independent bits (one of which was never used in heap pages anyway,
or at least hadn't been in a very long time). This gives us flexibility to
add the HOT notions of redirected and dead item pointers without requiring
anything so klugy as magic values of lp_off and lp_len. The state values
are chosen so that for the states currently in use (pre-HOT) there is no
change in the physical representation.
|
|
|
|
| |
SELECT on the target table. Per discussion.
|
|
|
|
|
|
| |
not all that exciting when the system catalogs are readable by all,
but some people try to lock them down, and would not like this sort of
end run ...
|
|
|
|
|
| |
but no permissions check at all is certainly no good.) Clean up usage
of some deprecated APIs.
|
|
|
|
|
| |
but no permissions check at all is certainly no good.) Clean up usage
of some deprecated APIs.
|
|
|
|
| |
usage of RelationNameGetTupleDesc().
|
|
|
|
| |
exposing user data to others, and clean up usage of deprecated APIs.
|
|
|
|
| |
(FD_SETSIZE - 10) rather than a hardwired number.
|
|
|
|
|
|
|
|
| |
padded encryption scheme. Formerly it would try to access res[(unsigned) -1],
which resulted in core dumps on 64-bit machines, and was certainly trouble
waiting to happen on 32-bit machines (though in at least the known case
it was harmless because that byte would be overwritten after return).
Per report from Ken Colson; fix by Marko Kreen.
|
| |
|
|
|
|
|
| |
the core additions. For the moment I diked it out of contrib/Makefile.
We should look at turning it into a backward-compatibility package.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
named pg_toast_temp_nnn, alongside the pg_temp_nnn schemas used for the temp
tables themselves. This allows low-level code such as the relcache to
recognize that these tables are indeed temporary, which enables various
optimizations such as not WAL-logging changes and using local rather than
shared buffers for access. Aside from obvious performance benefits, this
provides a solution to bug #3483, in which other backends unexpectedly held
open file references to temporary tables. The scheme preserves the property
that TOAST tables are not in any schema that's normally in the search path,
so they don't conflict with user table names.
initdb forced because of changes in system view definitions.
|
|
|
|
|
|
| |
and add a note about why. This is not tremendously important right now,
probably, but it will get more urgent if NUM_BUFFER_PARTITIONS is increased
as much as proposed.
|
|
|
|
|
|
| |
spaces in them.
ISHIDA Akio
|
|
|
|
| |
for 'bool'. Per buildfarm warnings.
|
|
|
|
| |
a warning but was outright wrong.
|
| |
|
|
|
|
|
| |
error messages look at least a little bit like the message style
guidelines say.
|
| |
|
|
|
|
| |
not-too-bright compilers. Per buildfarm results.
|
| |
|
| |
|
|
|
|
| |
three slightly different copies of this file?)
|