aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Remove premature attempt to constant-fold type coercion expressions.Tom Lane2003-04-10
| | | | | While usually safe, this fails if the coercion function needs the query snapshot to be set already. Per example from Nigel Andrews.
* First phase of work on array improvements. ARRAY[x,y,z] constructorTom Lane2003-04-08
| | | | | | | expressions, ARRAY(sub-SELECT) expressions, some array functions. Polymorphic functions using ANYARRAY/ANYELEMENT argument and return types. Some regression tests in place, documentation is lacking. Joe Conway, with some kibitzing from Tom Lane.
* Get rid of inappropriate flags in CPPFLAGS override --- these breakTom Lane2003-04-08
| | | | non-gcc compilers, and they would never belong in CPPFLAGS anyway.
* Mark TimeScales constants as double to avoid integer overflow in some compilers.Tom Lane2003-04-08
|
* Remove extraneous semicolons.Tom Lane2003-04-08
|
* Added some more informix compatibility functions.Michael Meskes2003-04-08
|
* Avoid primary key lookup (and lock) if foreign key does not changeJan Wieck2003-04-07
| | | | | | | | | | | | | | | | on UPDATE. This get's rid of the long standing annoyance that updating a row that has foreign keys locks all the referenced rows even if the foreign key values do not change. The trick is to actually do a check identical to NO ACTION after an eventually done UPDATE in the SET DEFAULT case. Since a SET DEFAULT operation should have moved referencing rows to a new "home", a following NO ACTION check can only fail if the column defaults of the referencing table resulted in the key we actually deleted. Thanks to Stephan. Jan
* Remove unnecessary dt2local() call.Tom Lane2003-04-07
|
* Generate pg_config.h.in by autoheader. Separate out manually editablePeter Eisentraut2003-04-06
| | | | parts. Standardize spelling of comments in pg_config.h.
* Fix compile problem with Win32 macro used inside another macro.Bruce Momjian2003-04-05
|
* Add Win32 path handling for / vs. \ and drive letters.Bruce Momjian2003-04-04
|
* Handle cp, rm, and exec for Win32.Bruce Momjian2003-04-04
|
* Fix some signed-vs-unsigned-int issues; make print_aligned_verticalTom Lane2003-04-04
| | | | safe for zero-column tables.
* Tighten up register usage for inline PPC version of tas().Tom Lane2003-04-04
|
* Put the isync where it's supposed to be.Tom Lane2003-04-04
|
* Avoid repeated computation of the constants date2j(1970, 1, 1) andTom Lane2003-04-04
| | | | | date2j(2000, 1, 1). Should make for some marginal speed improvement in date/time operations.
* Code review for pg_stat_get_backend_activity_start patch --- fixTom Lane2003-04-04
| | | | | return type, make protection condition agree with recent change to pg_stat_get_backend_activity, clean up documentation.
* Remove zero_damaged_pages from postgresql.conf.sample; the only way toTom Lane2003-04-03
| | | | | | | find out about it is to read the documentation that tells you how dangerous it is. Add default_transaction_read_only to documentation; seems to have been overlooked in patch that added read-only transactions. Clean up check_guc comparison script, which has been suffering bit rot.
* Prevent EXPLAIN (without ANALYZE) SELECT ... INTO from creating an INTOTom Lane2003-04-03
| | | | | table. Needed due to recent change that makes us call ExecutorStart even when not planning to carry out the query.
* Don't re-invent the strchr() wheel.Tom Lane2003-04-03
|
* Fix load_user/load_group to not leave dangling pointers around if theTom Lane2003-04-03
| | | | config files are present on one pass and not present on a later pass.
* const-ify functions used with completion_matches(), to suppressTom Lane2003-04-03
| | | | cast-away-const warnings from compilers pickier than gcc.
* Repair incorrect checking of grouped/ungrouped variables in the presenceTom Lane2003-04-03
| | | | of unnamed joins; per pghackers discussion 31-Mar-03.
* Add prototype for toupper/tolower().Bruce Momjian2003-04-03
|
* Fix buffer overrun in to_ascii(), per report from Guido Notari.Tom Lane2003-04-02
|
* Fix convSockAddr6to4(): eliminate bogus assumptions about byte ordering,Tom Lane2003-04-02
| | | | remove useless SockAddr_ntop() call. Per report from Andreas Pflug.
* Fix platform-dependent failure introduced by recent to_char changesTom Lane2003-04-02
| | | | (ye good olde uninitialized-local-variable).
* This is a derived file and should never have been added to CVS.Tom Lane2003-04-02
|
* Whack getaddrinfo() patch around until it works, more or less, onTom Lane2003-04-02
| | | | machines without IPv6. Or at least it works on HPUX 10.20 ...
* Add missing semicolon.Tom Lane2003-04-01
|
* More patches for informix compatibility.Michael Meskes2003-04-01
|
* Skip START WITH in sequence definition when it's the default value --Bruce Momjian2003-03-31
| | | | | | | | and hasn't been called yet. Fixes bug where it wasn't supplied (due to being NULL). Rod Taylor
* The following patch cleans up the deferred trigger mechanism. There isBruce Momjian2003-03-31
| | | | | | | | | an unneeded memory context and some variables that are not used anymore. It's pretty trivial and the regression tests pass fine. There's no change in functionality, only deletion of unused code. I left an empty function because maybe I'll need it for nested transactions. Alvaro Herrera
* TestConfiguration returns int, not bool. This mistake is relativelyTom Lane2003-03-31
| | | | | | | harmless on signed-char machines but would lead to core dump in the deadlock detection code if char is unsigned. Amazingly, this bug has been here since 7.1 and yet wasn't reported till now. Thanks to Robert Bruccoleri for providing the opportunity to track it down.
* Properly document default value of log_min_error_statement in postgresql.conf.Bruce Momjian2003-03-30
|
* Forgot two new files and one that was moved.Michael Meskes2003-03-30
|
* Moved Informix stuff to its own compat library. Interval datetype is now ↵Michael Meskes2003-03-30
| | | | fully functional.
* Simplify the socket handling code by supplying a replacement getaddrinfo()Peter Eisentraut2003-03-29
| | | | function if the OS doesn't provide one.
* [ Backpatch to 7.3.X.]Bruce Momjian2003-03-29
| | | | SSL_read/write can error needing ERROR_WANT_READ or ERROR_WANT_WRITE.
* [ Backpatch to 7.3.X.]Bruce Momjian2003-03-29
| | | | | | | | | | | typing error in src/backend/libpq/be-secure.c ??? Long Description In src/backend/libpq/be-secure.c: secure_write on SSL_ERROR_WANT_WRITE call secure_read instead secure_write again. May be is this a typing error? Sergey N. Yatskevich (syatskevich@n21lab.gosniias.msk.ru)
* Add code to apply some simple sanity checks to the header fields of aTom Lane2003-03-28
| | | | | | | | page when it's read in, per pghackers discussion around 17-Feb. Add a GUC variable zero_damaged_pages that causes the response to be a WARNING followed by zeroing the page, rather than the normal ERROR; this is per Hiroshi's suggestion that there needs to be a way to get at the data in the rest of the table.
* Fix NULL casting warning, pointed out by Joe ConwayBruce Momjian2003-03-28
|
* Fix bogus coding of SET DEFAULT ri triggers ... or at least make it lessTom Lane2003-03-27
| | | | bogus than it was. Per bug report from Adrian Pop.
* Add <stdlib> to add calloc() prototype.Bruce Momjian2003-03-27
|
* Fix syntax error in to_char fixes --- was defining variable in main codeBruce Momjian2003-03-27
| | | | block, ala C++.
* It may not be obvious to you, but the plpython regression testsBruce Momjian2003-03-27
| | | | | | | | | | | include output that vary depending on the python build one is running. Basically, the order of keys in a dictionary is non-deterministic, and that part of the test fails for me regularly. I rewrote the test to work around this problem, and include a patch file with that change and the change to the expected otuput as well. Mike Meyer
* New \d format:Bruce Momjian2003-03-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Example: test=# \d test Table "public.test" Column | Type | Modifiers --------+---------+----------- a | integer | not null Indexes: "test_pkey" PRIMARY KEY btree (a) Check Constraints: "$2" CHECK (a > 1) Foreign Key Constraints: "$1" FOREIGN KEY (a) REFERENCES parent(b) Rules: myrule AS ON INSERT TO test DO INSTEAD NOTHING Triggers: "asdf asdf" AFTER INSERT OR DELETE ON test FOR EACH STATEMENT EXECUTE PROCEDURE update_pg_pwd_and_pg_group(), mytrigger AFTER INSERT OR DELETE ON test FOR EACH ROW EXECUTE PROCEDURE update_pg_pwd_and_pg_group() I have minimised the double quoting of identifiers as much as I could easily, and I will submit another patch when I have time to work on it that will use a 'fmtId' function to determine it exactly. I think it's a significant improvement in legibility... Obviously the table example above is slightly degenerate in that not many tables in production have heaps of (non-constraint) triggers and rules. Christopher Kings-Lynne
* Add new file.Bruce Momjian2003-03-27
|
* Add new files.Bruce Momjian2003-03-27
|
* This patch implements holdable cursors, following the proposalBruce Momjian2003-03-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (materialization into a tuple store) discussed on pgsql-hackers earlier. I've updated the documentation and the regression tests. Notes on the implementation: - I needed to change the tuple store API slightly -- it assumes that it won't be used to hold data across transaction boundaries, so the temp files that it uses for on-disk storage are automatically reclaimed at end-of-transaction. I added a flag to tuplestore_begin_heap() to control this behavior. Is changing the tuple store API in this fashion OK? - in order to store executor results in a tuple store, I added a new CommandDest. This works well for the most part, with one exception: the current DestFunction API doesn't provide enough information to allow the Executor to store results into an arbitrary tuple store (where the particular tuple store to use is chosen by the call site of ExecutorRun). To workaround this, I've temporarily hacked up a solution that works, but is not ideal: since the receiveTuple DestFunction is passed the portal name, we can use that to lookup the Portal data structure for the cursor and then use that to get at the tuple store the Portal is using. This unnecessarily ties the Portal code with the tupleReceiver code, but it works... The proper fix for this is probably to change the DestFunction API -- Tom suggested passing the full QueryDesc to the receiveTuple function. In that case, callers of ExecutorRun could "subclass" QueryDesc to add any additional fields that their particular CommandDest needed to get access to. This approach would work, but I'd like to think about it for a little bit longer before deciding which route to go. In the mean time, the code works fine, so I don't think a fix is urgent. - (semi-related) I added a NO SCROLL keyword to DECLARE CURSOR, and adjusted the behavior of SCROLL in accordance with the discussion on -hackers. - (unrelated) Cleaned up some SGML markup in sql.sgml, copy.sgml Neil Conway
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 05:44:42 +0000