- 02 9月, 2004 12 次提交
-
-
由 Bruce Momjian 提交于
> * Consider using hash buckets to do DISTINCT, rather than sorting > > This would be beneficial when there are few distinct values.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
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
-
由 Bruce Momjian 提交于
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
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
EXCEPT constructs.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
It's still useless because it tests a standalone backend, but at least the bit rot is repaired.
-
由 Tom Lane 提交于
systems. Magnus Hagander.
-
- 01 9月, 2004 11 次提交
-
-
由 Tom Lane 提交于
-
由 Dennis Bjorklund 提交于
-
由 Tom Lane 提交于
of an object owner and the SQL spec's treatment of these rights.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
<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>
-
由 Bruce Momjian 提交于
Greg Sabino Mullane
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
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.
-
由 Tom Lane 提交于
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.
-
由 Tom Lane 提交于
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.
-
由 Tom Lane 提交于
relation is already opened by smgr.
-
- 31 8月, 2004 13 次提交
-
-
由 Tom Lane 提交于
would always be already open at the smgr level. Per bug report from Fabien Coelho.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
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.
-
由 PostgreSQL Daemon 提交于
tag configure beta2
-
由 Tom Lane 提交于
the slock_t datatype (ie, declared type smaller than what the hardware TAS instruction needs).
-
由 Tom Lane 提交于
info was apparently mistranscribed in s_lock code rearrangement.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
for the tutorial files right here.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
startup, just to be sure that there's no leftover junk there.
-
由 Tom Lane 提交于
only within COMMIT or ABORT records.
-
由 Bruce Momjian 提交于
< * Fix oid2name and dbsize for tablespaces
-
- 30 8月, 2004 4 次提交
-
-
由 Tom Lane 提交于
write into a high-numbered segment of a relation that was later deleted. We need to temporarily recreate missing segment files, instead of failing.
-
由 Tom Lane 提交于
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.
-
由 Bruce Momjian 提交于
Dave Page
-
由 Bruce Momjian 提交于
-