| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
| |
> * Consider using hash buckets to do DISTINCT, rather than sorting
>
> This would be beneficial when there are few distinct values.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Windows.
Recap: When running on a localized windows version, the timezone name
returned is also localized, and therefor does not match our lookup
table.
Solution: The registry contains both the name of the timezone in english
and the localized name. The patch adds code to scan the registry for the
localized name and gets the english name from that, and then rescans the
table.
I have tested this on a Swedish WinXP, and it works without problems.
The registry layout is the same in Win2k, but I haven't specifically
tested it. It's also the same on different languages but again only
Swedish is tested.
Magnus Hagander
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tablespaces correctly, and is quite restricted on objects covered (only
tables and databases, but not tablespaces and indexes).
The attached patch contributes:
- database_size(name)
- relation_size(text)
These are the well-known functions, tablespace-aware.
- pg_tablespace_size(oid)
- pg_database_size(oid)
- pg_relation_size(oid)
Tablespace-aware implementations, used by the upper functions.
pg_relation_size will report sizes of indexes as well.
- pg_size_pretty(bigint)
Formatting of sizes, to display '146MB' instead of '152885668'
Andreas Pflug
|
| | |
|
| |
|
|
| |
EXCEPT constructs.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
It's still useless because it tests a standalone backend, but at least
the bit rot is repaired.
|
| |
|
|
| |
systems. Magnus Hagander.
|
| | |
|
| | |
|
| |
|
|
| |
of an object owner and the SQL spec's treatment of these rights.
|
| | |
|
| |
|
|
|
|
| |
<P>In pre-8.0 releases, indexes often can not be used unless the data
types exactly match the index's column types. This is particularly
true of int2, int8, and numeric column indexes.</P>
|
| |
|
|
| |
Greg Sabino Mullane
|
| | |
|
| |
|
|
|
|
|
| |
use of already-freed strings, other silliness. Also fix reporting of
config file syntax errors so that it actually works reasonably well
(eg, points at the correct line). Use palloc instead of malloc for
temporary storage to reduce code clutter.
|
| |
|
|
|
|
|
| |
not supposed to (fixes problem with postmaster aborting due to mistaken
postgresql.conf change); don't call superuser() when not inside a
transaction (fixes coredump when, eg, try to set log_statement from
PGOPTIONS); some message style guidelines enforcement.
|
| |
|
|
|
|
|
| |
default tablespace --- they should always go in the database's default
tablespace. Adjust heap_create() API so that it is passed the relkind
to make this easier; should simplify any further tweaking of the same
sort.
|
| |
|
|
| |
relation is already opened by smgr.
|
| |
|
|
|
| |
would always be already open at the smgr level. Per bug report from
Fabien Coelho.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
to allow DBA to choose the form in which log filenames reflect the
current time. Also allow for truncating instead of appending to
pre-existing files --- this is convenient when the log filename pattern
rewrites the same names cyclically. Per Ed L.
|
| | |
|
| |
|
|
|
| |
the slock_t datatype (ie, declared type smaller than what the hardware
TAS instruction needs).
|
| |
|
|
| |
info was apparently mistranscribed in s_lock code rearrangement.
|
| | |
|
| |
|
|
| |
for the tutorial files right here.
|
| | |
|
| |
|
|
| |
startup, just to be sure that there's no leftover junk there.
|
| |
|
|
| |
only within COMMIT or ABORT records.
|
| |
|
|
| |
< * Fix oid2name and dbsize for tablespaces
|
| |
|
|
|
|
| |
write into a high-numbered segment of a relation that was later deleted.
We need to temporarily recreate missing segment files, instead of
failing.
|
| |
|
|
|
|
|
|
| |
during replay of CREATE DATABASE as well as the first time around.
Else it's possible that the copy operation will copy obsolete blocks.
We are still a long way from guaranteeing anything about using a
recently-written database as a CREATE template, but this seems needed
to ensure the existing behavior holds up during replay.
|
| |
|
|
| |
Dave Page
|
| | |
|
| | |
|
| |
|
|
| |
be written with quotes. Minor copy-editing too.
|
| |
|
|
|
|
|
|
| |
Fix TablespaceCreateDbspace() to be able to create a dummy directory
in place of a dropped tablespace's symlink. This eliminates the open
problem of a PANIC during WAL replay when a replayed action attempts
to touch a file in a since-deleted tablespace. It also makes for a
significant improvement in the usability of PITR replay.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
a more tolerable limit on the number of subtransactions or deleted files
in COMMIT and ABORT records. Buy back the extra space by eliminating the
xl_xact_prev field, which isn't being used for anything and is rather
unlikely ever to be used for anything.
This does not force initdb, but you do need to do pg_resetxlog if you
want to upgrade an existing 8.0 installation without initdb.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Win32 WaitForMultipleObjects:
ret = WaitForMultipleObjects(win32_numChildren, win32_childHNDArray,
FALSE, 0);
Problem is 'win32_numChildren' could be more then 64 ( function supports
), problem basically arise ( kills postgres ) when you create more then
64 connections and terminate some of them sill leaving more then 64.
Claudio Natoli
|
