summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Tweak a few of the most heavily used function call points to zero outTom Lane2002-10-043-188/+261
| | | | | | | | | | just the significant fields of FunctionCallInfoData, rather than MemSet'ing the whole struct to zero. Unused positions in the arg[] array will thereby contain garbage rather than zeroes. This buys back some of the performance hit from increasing FUNC_MAX_ARGS. Also tweak tuplesort.c code for more speed by marking some routines 'inline'. All together these changes speed up simple sorts, like count(distinct int4column), by about 25% on a P4 running RH Linux 7.2.
* Hack to make it possible to load CREATE CONSTRAINT TRIGGER commands thatTom Lane2002-10-032-6/+120
| | | | | are missing the FROM clause (due to a long-ago pg_dump bug). Patch by Stephan Szabo, minor tweaking by Tom Lane.
* In a bootstrap process or standalone backend, set MaxBackends = 1Tom Lane2002-10-031-5/+8
| | | | to avoid unnecessary consumption of semaphores.
* Avoid palloc(0) when MaxBackends = 1.Tom Lane2002-10-031-3/+5
|
* Restore NOTICEs that were mistakenly removed from triggers regressionTom Lane2002-10-032-2/+8
| | | | | test expected output. Tweak contrib/spi Makefile so that refint.so is by default built with appropriate NOTICE support for regression testing.
* Add SSL documentation info to README.SSLBruce Momjian2002-10-031-1/+403
|
* The attached patch fixes a number of issues related to compiling theBruce Momjian2002-10-0316-64/+94
| | | | | | | | | | | | | | | | | | client utilities (libpq.dll and psql.exe) for win32 (missing defines, adjustments to includes, pedantic casting, non-existent functions) per: http://developer.postgresql.org/docs/postgres/install-win32.html. It compiles cleanly under Windows 2000 using Visual Studio .net. Also compiles clean and passes all regression tests (regular and contrib) under Linux. In addition to a review by the usual suspects, it would be very desirable for someone well versed in the peculiarities of win32 to take a look. Joe Conway
* This patch removes two unused global variables from globals.cBruce Momjian2002-10-032-9/+2
| | | | Neil Conway
* Re-enable pg_resetxlog to accept -l values in hexadecimal (it used toTom Lane2002-10-021-16/+55
| | | | | | be able to do that, but the ability seems to have got lost in the shuffle). Add a -o nextOID switch for completeness. Improve the documentation to explain how and why to use these switches.
* pg_resetxlog was missing support for the pg_control fields added in 7.3.Tom Lane2002-10-021-1/+15
|
* Alter scale selection for NUMERIC division and transcendental functionsTom Lane2002-10-023-133/+348
| | | | | | so that precision of result is always at least as good as you'd get from float8 arithmetic (ie, always at least 16 digits of accuracy). Per pg_hackers discussion a few days ago.
* Turn GUC log_min_error_statement off by default by setting it to PANIC.Bruce Momjian2002-10-021-2/+13
|
* test files added by Kris JurkaDave Cramer2002-10-013-0/+397
|
* Pass less-unsafe parameters to Darwin's NSLinkModule. While this change ↵Tom Lane2002-10-011-2/+4
| | | | prevents a backend coredump when loading a broken shlib, it also seems to suppress the error messages that might help debug the problem :-(. Perhaps someone would like to supply a 'linkEdit' hook to get the best of both worlds. But in the meantime, backend crash trumps error reporting.
* Fixed test suite to call PoolingDataSourceTest which was missedBarry Lind2002-10-011-2/+2
| | | | | Modified Files: OptionalTestSuite.java
* schema awareness patch provided by Kris JurkaDave Cramer2002-10-019-896/+1353
|
* Add Bear's SSL comments.Bruce Momjian2002-09-291-0/+28
|
* Make the world at least somewhat safe for zero-column tables, andTom Lane2002-09-286-81/+64
| | | | | remove the special case in ALTER DROP COLUMN to prohibit dropping a table's last column.
* ARGH!Tom Lane2002-09-271-18/+38
| | | | | | | | Vacuum must not advance pg_database.datvacuumxid nor truncate CLOG unless it's processed *all* tables in the database. Vacuums run by unprivileged users don't count. (Beats head against nearest convenient wall...)
* > Fix clusterdb to be schema-awareBruce Momjian2002-09-271-2/+2
| | | | | | Please apply the patch attached and this should be solved. Alvaro Herrera
* Use heap_formtuple not heap_addheader to construct pg_index tuples.Tom Lane2002-09-271-46/+42
| | | | | heap_addheader is wrong because it doesn't cope with varlena fields, notably indpred.
* Don't mess with HEAP_XMAX_INVALID in heaptuple.c routines; there isTom Lane2002-09-271-10/+14
| | | | | | no reason to worry about the tuple commit status bits until the tuple is inserted in a relation by heapam.c. Also, improve comments for heap_addheader().
* Have -d5 -d0 not affect the extra variables set with -d5.Bruce Momjian2002-09-271-18/+21
|
* Make postgres -d0 set server_min_messages to notice. Reset doesn't workBruce Momjian2002-09-271-5/+6
| | | | at this area in the code.
* Ensure that before truncating CLOG, we force a checkpoint even if noTom Lane2002-09-265-25/+26
| | | | | | recent WAL activity has occurred. Without this, it's possible that a later crash might leave tuples on disk with un-updated commit status bits.
* Fix problems with loss of tuple commit status bits during WAL redo ofTom Lane2002-09-263-28/+41
| | | | | | | | | VACUUM FULL tuple moves. Store full-width t_infomask in WAL, rather than storing low 8 bits and expecting to be able to reconstruct upper bits. While at it, remove redundant t_oid field from WAL headers (the OID, if present, is now recorded in the data portion of the tuple). WAL version number bumped --- this does not force an initdb, you can instead run pg_resetxlog after a clean shutdown of the old postmaster.
* Back out /pl memory leak patch. Wait for new version.Bruce Momjian2002-09-264-25/+4
|
* Clean up SSL compiler warnings.Bruce Momjian2002-09-261-1/+7
|
* I have attached the pltcl patch again, just in case. For the sake of clarityBruce Momjian2002-09-264-4/+25
| | | | | | | | | | | | | | let's say this patch superscedes the previous one. I have also attached a patch addressing the similar memory leak problem in plpython. This includes a slight adjustment of the tests in the source directory. The patch also includes a cosmetic change to remove a compiler warning although I think the change makes the code look worse though. BTW, by my reckoning the memory leak would occur with prepared plans and without. If that is not the case then I've been barking up the wrong tree. Nigel J. Andrews
* This patch removes a use of uninitialized memory in lmgr/lock.c, byBruce Momjian2002-09-261-1/+2
| | | | | | adding a missing sprintf(). Neil Conway
* Pass postmaster -d down to the postgres backend to trigger special -dBruce Momjian2002-09-262-5/+17
| | | | handling in the backend.
* Allow SSL to work withouth client-side certificate infrastructure.Bruce Momjian2002-09-262-2/+16
|
* Remove ShutdownBufferPoolAccess exit callback, and do the work inTom Lane2002-09-256-34/+43
| | | | | | | | | ProcKill instead, where we still have a PGPROC with which to wait on LWLocks. This fixes 'can't wait without a PROC structure' failures occasionally seen during backend shutdown (I'm surprised they weren't more frequent, actually). Add an Assert() to LWLockAcquire to help catch any similar mistakes in future. Fix failure to update MyProcPid for standalone backends and pgstat processes.
* Applied patch from Aaron Mulder (ammulder@alumni.princeton.edu) that fixesBarry Lind2002-09-2520-31/+1023
| | | | | | | | | | | | | | | | | | | | | | | | | | jdbc datasource support for jdk1.4/jdbc3 Modified Files: jdbc/build.xml jdbc/org/postgresql/Driver.java.in jdbc/org/postgresql/jdbc2/optional/BaseDataSource.java jdbc/org/postgresql/jdbc2/optional/PGObjectFactory.java jdbc/org/postgresql/jdbc2/optional/PooledConnectionImpl.java jdbc/org/postgresql/jdbc2/optional/PoolingDataSource.java jdbc/org/postgresql/test/jdbc2/optional/BaseDataSourceTest.java jdbc/org/postgresql/test/jdbc2/optional/OptionalTestSuite.java jdbc/org/postgresql/test/jdbc3/Jdbc3TestSuite.java Added Files: jdbc/org/postgresql/jdbc3/Jdbc3ConnectionPool.java jdbc/org/postgresql/jdbc3/Jdbc3ObjectFactory.java jdbc/org/postgresql/jdbc3/Jdbc3PooledConnection.java jdbc/org/postgresql/jdbc3/Jdbc3PoolingDataSource.java jdbc/org/postgresql/jdbc3/Jdbc3SimpleDataSource.java jdbc/org/postgresql/test/jdbc2/optional/PoolingDataSourceTest.java jdbc/org/postgresql/test/jdbc3/Jdbc3ConnectionPoolTest.java jdbc/org/postgresql/test/jdbc3/Jdbc3PoolingDataSourceTest.java jdbc/org/postgresql/test/jdbc3/Jdbc3SimpleDataSourceTest.java jdbc/org/postgresql/test/util/MiniJndiContext.java jdbc/org/postgresql/test/util/MiniJndiContextFactory.java
* Change default privileges for languages and functions to be PUBLIC USAGETom Lane2002-09-247-22/+46
| | | | | and PUBLIC EXECUTE, respectively. Per discussion about easing updates from prior versions.
* Update some obsolete comments and column descriptions.Tom Lane2002-09-241-9/+7
|
* Remove useless O_DIROPEN stuff.Peter Eisentraut2002-09-241-4/+0
|
* Tweak conversion names to follow the established naming scheme, andPeter Eisentraut2002-09-243-103/+103
| | | | document that scheme.
* Add missing correction of sublevelsup when pulling up a subquery.Tom Lane2002-09-241-3/+9
| | | | | | Fixes problem with cases like SELECT * FROM foo t WHERE NOT EXISTS (SELECT remoteid FROM (SELECT f1 as remoteid FROM foo WHERE f1 = t.f1) AS t1)
* Further thinking about heap_mark4update: in HeapTupleSelfUpdated case,Tom Lane2002-09-232-2/+8
| | | | | | | | | executor should not return the tuple as successfully marked, because in fact it's been deleted. Not clear that this case has ever been seen in practice (I think you'd have to write a SELECT FOR UPDATE that calls a function that deletes some row the SELECT will visit later...) but we should be consistent. Also add comments to several other places that got it right but didn't explain what they were doing.
* Move PyGreSQL usage documentation from README into DocBook. Some otherPeter Eisentraut2002-09-232-887/+5
| | | | editing.
* Disallow VACUUM, ANALYZE, TRUNCATE on temp tables belonging to otherTom Lane2002-09-235-5/+64
| | | | | backends. Given that temp tables now store data locally in the local buffer manager, these things are not going to work safely.
* Obviously noone has ever tested the doubling of availiable result idsBruce Momjian2002-09-231-1/+4
| | | | | | | | | | | | | | | | | | | up to reaching the hard limit. After opening 16(=current REST_START value) results via pg_exec, the next pg_exec tries to find an empty slot forever :-( . In PgSetResultId file pgtclId.c in the for loop there has to be done a break, if res_max ist reached. The piece of code should look like if (resid == connid->res_max) { resid = 0; break; /* the break as to be added */ } now everything works (double available results after reaching RES_START up to reaching RES_HARD_MAX) Gerhard Hintermayer
* Get rid of bogus use of heap_mark4update in reindex operations (cf.Tom Lane2002-09-234-169/+133
| | | | | recent bug report). Fix processing of nailed-in-cache indexes; it appears that REINDEX DATABASE has been broken for months :-(.
* In UpdateStats(), don't bother to update the pg_class row if it alreadyTom Lane2002-09-221-54/+40
| | | | | | | | contains the correct statistics. This is a partial solution for the problem of allowing concurrent CREATE INDEX commands: unless they commit at nearly the same instant, the second one will see the first one's pg_class updates as committed, and won't try to update again, thus avoiding the 'tuple concurrently updated' failure.
* Remove commas for compatibility with newer releases of bison.Tom Lane2002-09-221-18/+18
|
* Remove commas for compatibility with newer bisons.Tom Lane2002-09-221-47/+47
|
* Remove commas from %type and %token lists, for compatibility with newerTom Lane2002-09-221-161/+161
| | | | versions of bison.
* Translation updates, some messages tweaked.Peter Eisentraut2002-09-2218-1582/+2709
|
* RelationClearRelation must reset rd_targblock and update rd_nblocksTom Lane2002-09-221-2/+6
| | | | | | even when dealing with a nailed-in-cache relation; otherwise, following VACUUM truncation of a system catalog, other backends might have unreasonably large values of these fields.
View Lorry Controller Status