- 01 8月, 2003 5 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
might have inherited from the environment that would possibly cause psql to fail to connect to the temp installation properly. Per trouble report from Markus Bertheau 7/1/03.
-
由 Tom Lane 提交于
function is not found. Also, make all the PL libraries have initialization functions with standard names. Patch from Joe Conway.
-
由 Tom Lane 提交于
the actual logical structure and quoting rules being used. Fixes bug reported by Chris K-L on 7/8/03.
-
- 31 7月, 2003 13 次提交
-
-
由 Bruce Momjian 提交于
> * Implement dirty reads or shared row locks and use them in RI triggers
-
由 Bruce Momjian 提交于
> * Implement dirty reads or shared locks and use them in RI triggers
-
由 Bruce Momjian 提交于
Rod Taylor
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
There is an option "-s oldname=newname", which changes the old field name of the dbf-file to the newname in PostgeSQL. If the length of the new name is 0, the field is skiped. If you want to skip the first field of the dbf-file, you get the wildest error-messages from the backend. dbf2pg load the dbf-file via "COPY tablename FROM STDIN". If you skip the first field, it is an \t to much in STDIN. A fix could be an counter j=0, which increments only, if a field is imported (IF (strlen(fields[h].db_name)> 0) j++. And only if j > 1 (if an other field is imported) the \t is printed. An other small bug in the README: -s start Specify the first record-number in the xBase-file we will insert. should be -e start Specify the first record-number in the xBase-file we will insert. Thomas Behr
-
由 Tom Lane 提交于
Patch from Andreas Pflug.
-
由 Bruce Momjian 提交于
> * Allow server log information to be output as INSERT statements
-
由 Tom Lane 提交于
float8smaller, float8larger (and thereby the MIN/MAX aggregates on these datatypes) to agree with the datatypes' comparison operations as regards NaN handling. In all these datatypes, NaN is arbitrarily considered larger than any normal value ... but MIN/MAX had not gotten the word. Per recent discussion on pgsql-sql.
-
由 Bruce Momjian 提交于
> * Allow log lines to include session-level information, like database and user
-
由 Tom Lane 提交于
error, if any input element is NULL. This is not what we ultimately want, but until arrays can have NULL elements, it will have to do. Patch from Joe Conway.
-
由 Bruce Momjian 提交于
> * Add database name and user name to logging options
-
由 Tom Lane 提交于
wait for the postmaster to actually exit. Otherwise running repeated 'make check's tends to misbehave, because we try to remove and recreate the data directory while the old PM is still alive.
-
- 30 7月, 2003 2 次提交
-
-
由 Tom Lane 提交于
bottom. Otherwise we fail to moveright when the root page was split while we were "in flight" to it. This is not a significant problem when the root is above the leaf level, but if the root was also a leaf (ie, a single-page index just got split) we may return the wrong leaf page to the caller, resulting in failure to find a key that is in fact present. Bug has existed at least since 7.1, probably forever.
-
由 Tom Lane 提交于
CREATE TABLE (or ALTER TABLE SET DEFAULT), rather than postponing it to the time that the default is inserted into an INSERT command by the rewriter. This reverses an old decision that was intended to make the world safe for writing f1 timestamp default 'now' but in fact merely made the failure modes subtle rather than obvious. Per recent trouble report and followup discussion. initdb forced since there is a chance that stored default expressions will change.
-
- 29 7月, 2003 6 次提交
-
-
由 Tom Lane 提交于
reason not to: it fails for an 'invalid' abstime. Per bug report of today's date.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
heuristic determination of day vs month in date/time input. Add the ability to specify that input is interpreted as yy-mm-dd order (which formerly worked, but only for yy greater than 31). DateStyle's input component now has the preferred spellings DMY, MDY, or YMD; the older keywords European and US are now aliases for the first two of these. Per recent discussions on pgsql-general.
-
由 Tom Lane 提交于
these things were added at different times by different people ;-). Includes Aizaz Ahmed's patch to remove duplicate array in help_config.c.
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
materialized. New items have been added to GucContext and GucSource enums, but of course they were not added to the corresponding GucContextName[] and GucSourceName[] arrays in the patch. Here's a new patch to fix the resulting bugs. Joe Conway
-
- 28 7月, 2003 13 次提交
-
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
internal errors.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
I'd have to disagree with regards to the memory leaks not being worth a mention - any such leak can cause problems when the PostgreSQL installation is either unattended, long-living andor has very high connection levels. Half a kilobyte on start-up isn't negligible in this light. Regards, Lee. Tom Lane writes: > Lee Kindness <lkindness@csl.co.uk> writes: > > Guys, attached is a patch to fix two memory leaks on start-up. > > I do not like the changes to miscinit.c. In the first place, it is not > a "memory leak" to do a one-time allocation of state for a proc_exit > function. A bigger complaint is that your proposed change introduces > fragile coupling between CreateLockFile and its callers, in order to > save no resources worth mentioning. More, it introduces an assumption > that the globals directoryLockFile and socketLockFile don't change while > the postmaster is running. UnlinkLockFile should unlink the file that > it was originally told to unlink, regardless of what happens to those > globals. > > If you are intent on spending code to free stuff just before the > postmaster exits, a better fix would be for UnlinkLockFile to free its > string argument after using it. Lee Kindness
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
- 27 7月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
-