- 08 Dec, 2005 17 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
> * Teodor is Teodor Sigaev <teodor@sigaev.ru>
-
Bruce Momjian authored
< * Claudio is Claudio Natoli <claudio.natoli@memetrics.com> 1166d1164 < * Hiroshi is Hiroshi Inoue <Inoue@tpf.co.jp>
-
Bruce Momjian authored
postgres problems due to readline. The attached patch replaces that section of it with better ways of handling the problem. Seneca Cunningham
-
Bruce Momjian authored
DROP CONSTRAINT This form drops constraints on a table. Currently, constraints on tables are not required to have unique names, so there may be more than one constraint matching the specified name. All matching constraints will be dropped. To my knowledge, it is no longer possible to create constraints with the same name for the same relation. When you create a constraint and specify the same name explictly, an error is raised. Implicit constraint creation won't choose an existing name either and up to now you could not rename a constraint. Renaming works with the patch I sent in a few hours ago but this patch as well won't allow constraints with identical names on the same relation. The attached patch thus removes the note in the docs. Joachim Wieland
-
Bruce Momjian authored
> Now, the arguments of the drop function can be tab completed. for example > > drop function strpos ( > <press tab> > drop FUNCTION strpos (text, text) > > or: > > wsdb=# drop FUNCTION length ( > bit) bytea) character) lseg) path) text) > <press c> > wsdb# DROP FUNCTION length ( character) > > I think that this patch should be rather useful. At it least I hate > always to type all the arguments of the dropped functions. > > 2) Also some fixes applied for the > CREATE INDEX syntax > > now the parenthesises are inserted by tab pressing. > suppose I have the table q3c: Sergey E. Koposov
-
Peter Eisentraut authored
-
Bruce Momjian authored
-
Peter Eisentraut authored
-
Bruce Momjian authored
Also, better mark section headings. kdio@uenf.br
-
Peter Eisentraut authored
-
Tom Lane authored
error. This probably explains bug #2099 and could also account for mysterious VACUUM hangups.
-
Bruce Momjian authored
support for the dbf2pg contrib module. The submitter created a patch which replaces the silent ignoring of -F (when iconv support is disabled) with a meaningful warning. Martin Pitt
-
Bruce Momjian authored
that are the same as column names used in the function.
-
Bruce Momjian authored
I have the problem, when building by MS-VC6. An error occurs in the 8.1.0 present source codes. nmake -f win32.mak ..\..\port\getaddrinfo.c(244) : error C2065: 'WSA_NOT_ENOUGH_MEMORY' ..\..\port\getaddrinfo.c(342) : error C2065: 'WSATYPE_NOT_FOUND' This is used by winsock2.h. However, Construction of a windows base is winsock.h. Then, Since MinGW has special environment, this is right. but, it is not found in VC6. Furthermore, in getaddrinfo.c, IPV6-API is used by LoadLibraryA("ws2_32"); Referring to of dll the external memory generates this violation by VC6 specification. I considered whether the whole should have been converted into winsock2. However, Now, DLL of MinGW creation operates wonderfully as it is. That's right, it has pliability by replacement of simple DLL. Then, I propose the system using winsock(non IPV6) in construction of VC6. Hiroshi Saito
-
Tom Lane authored
-
Teodor Sigaev authored
-
- 07 Dec, 2005 10 commits
-
-
Tom Lane authored
_bt_checkkeys(), instead of checking it in the top-level nbtree.c routines as formerly. This saves a little bit of loop overhead, but more importantly it lets us skip performing the index key comparisons for dead tuples.
-
Tom Lane authored
checks, which were once needed because PageGetMaxOffsetNumber would fail on empty pages, but are now just redundant. Also, don't set up local variables that aren't needed in the fast path --- most of the time, we only need to advance offnum and not step across a page boundary. Motivated by noticing _bt_step at the top of OProfile profile for a pgbench run.
-
Bruce Momjian authored
< at initdb time or optionally later. > at initdb time or optionally later. Consider O_SYNC when > O_DIRECT exists.
-
Tom Lane authored
-
Tom Lane authored
-
Tom Lane authored
-
Bruce Momjian authored
-
Teodor Sigaev authored
-
Teodor Sigaev authored
- allow ~ in filenames - -8.2.1 now is '-' and '8.2.1' instead of '-8.2' '.' '3' - '.text' now is not a file
-
Bruce Momjian authored
-
- 06 Dec, 2005 13 commits
-
-
Tom Lane authored
SLRU area. The number of slots is still a compile-time constant (someday we might want to change that), but at least it's a different constant for each SLRU area. Increase number of subtrans buffers to 32 based on experimentation with a heavily subtrans-bashing test case, and increase number of multixact member buffers to 16, since it's obviously silly for it not to be at least twice the number of multixact offset buffers.
-
Bruce Momjian authored
-
Bruce Momjian authored
> * Add GUC variable to run a command on database panic or > smart/fast/immediate shutdown
-
Bruce Momjian authored
-
Bruce Momjian authored
-
Bruce Momjian authored
file. Backpatch to 8.1.X. Paul Lindner
-
Bruce Momjian authored
non-ascii convert to & escapes
-
Bruce Momjian authored
the latest release notes there is a latin1 character that shouldn't be there so I made a patch to fix that. This patch also fixes some old entries that uses o instead of ö (which is also wrong but not as bad as including a latin1 character in the sgml file). Dennis Bj?rklund
-
Bruce Momjian authored
Backpatch to 8.1.X.
-
Teodor Sigaev authored
-
Tom Lane authored
lock, not exclusive, if the desired page is already in memory. This can be demonstrated to be a significant win on the pg_subtrans cache when there is a large window of open transactions. It should be useful for pg_clog as well. I didn't try to make GetMultiXactIdMembers() use the code, as that would have taken some restructuring, and what with the local cache for multixact contents it probably wouldn't really make a difference. Per my recent proposal.
-
Tom Lane authored
clauses even if it's an outer join. This is a corner case since such clauses could only arise from weird OUTER JOIN ON conditions, but worth fixing. Per example from Ron at cheapcomplexdevices.com.
-
Tom Lane authored
-