- 30 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
that the types of untyped string-literal constants are deduced (ie, when coerce_type is applied to 'em, that's what the type must be). Remove the ancient hack of storing the input Param-types array as a global variable, and put the info into ParseState instead. This touches a lot of files because of adjustment of routine parameter lists, but it's really not a large patch. Note: PREPARE statement still insists on exact specification of parameter types, but that could easily be relaxed now, if we wanted to do so.
-
- 28 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
I had inadvertently omitted it while rearranging things to support length-counted incoming messages. Also, change the parser's API back to accepting a 'char *' query string instead of 'StringInfo', as the latter wasn't buying us anything except overhead. (I think when I put it in I had some notion of making the parser API 8-bit-clean, but seeing that flex depends on null-terminated input, that's not really ever gonna happen.)
-
- 25 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
rewritten and the protocol is changed, but most elog calls are still elog calls. Also, we need to contemplate mechanisms for controlling all this functionality --- eg, how much stuff should appear in the postmaster log? And what API should libpq expose for it?
-
- 22 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
have length words. COPY OUT reimplemented per new protocol: it doesn't need \. anymore, thank goodness. COPY BINARY to/from frontend works, at least as far as the backend is concerned --- libpq's PQgetline API is not up to snuff, and will have to be replaced with something that is null-safe. libpq uses message length words for performance improvement (no cycles wasted rescanning long messages), but not yet for error recovery.
-
- 19 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
have length counts, and COPY IN data is packetized into messages.
-
- 18 4月, 2003 1 次提交
-
-
由 Tom Lane 提交于
with variable-width fields. No more truncation of long user names. Also, libpq can now send its environment-variable-driven SET commands as part of the startup packet, saving round trips to server.
-
- 25 3月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
when autocommit is off, and document grouping when autocommit is on.
-
- 22 3月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Cleans up blank query handling to be more consistent.
-
- 20 3月, 2003 1 次提交
-
-
由 Bruce Momjian 提交于
Add ALTER SEQUENCE to modify min/max/increment/cache/cycle values Also updated create sequence docs to mention NO MINVALUE, & NO MAXVALUE. New Files: doc/src/sgml/ref/alter_sequence.sgml src/test/regress/expected/sequence.out src/test/regress/sql/sequence.sql ALTER SEQUENCE is NOT transactional. It behaves similarly to setval(). It matches the proposed SQL200N spec, as well as Oracle in most ways -- Oracle lacks RESTART WITH for some strange reason. -- Rod Taylor <rbt@rbt.ca>
-
- 10 3月, 2003 1 次提交
-
-
由 Tom Lane 提交于
utility statement (DeclareCursorStmt) with a SELECT query dangling from it, rather than a SELECT query with a few unusual fields in it. Add code to determine whether a planned query can safely be run backwards. If DECLARE CURSOR specifies SCROLL, ensure that the plan can be run backwards by adding a Materialize plan node if it can't. Without SCROLL, you get an error if you try to fetch backwards from a cursor that can't handle it. (There is still some discussion about what the exact behavior should be, but this is necessary infrastructure in any case.) Along the way, make EXPLAIN DECLARE CURSOR work.
-
- 06 3月, 2003 1 次提交
-
-
由 Tom Lane 提交于
at database shutdown, and then load it again at database startup. This preserves our hard-won knowledge of free space across restarts (given an orderly shutdown, that is).
-
- 10 2月, 2003 1 次提交
-
-
由 Tom Lane 提交于
codes, per discussion from last March. parse.h should now be included *only* by gram.y, scan.l, keywords.c, parser.c. This prevents surprising misbehavior after seemingly-trivial grammar adjustments.
-
- 02 1月, 2003 1 次提交
-
-
由 Tom Lane 提交于
target function. Also, move SetQuerySnapshot() call to avoid assert failure when a fastpath call is attempted in an aborted transaction.
-
- 06 12月, 2002 3 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
ALTER DOMAIN .. SET / DROP DEFAULT ALTER DOMAIN .. ADD / DROP CONSTRAINT New files: - doc/src/sgml/ref/alter_domain.sgml Rod Taylor
-
- 20 11月, 2002 1 次提交
-
-
由 Bruce Momjian 提交于
"canceled", so I changed the one remaining usage of the British spelling ("cancelled") over to the former, and updated the translation files appropriately. Neil Conway
-
- 15 11月, 2002 2 次提交
-
-
由 Bruce Momjian 提交于
! #show_parser_stats = false ! #show_planner_stats = false ! #show_executor_stats = false ! #show_statement_stats = false TO: ! #log_parser_stats = false ! #log_planner_stats = false ! #log_executor_stats = false ! #log_statement_stats = false
-
由 Bruce Momjian 提交于
of log_ settings.
-
- 01 11月, 2002 1 次提交
-
-
由 Tom Lane 提交于
between signal handler and enable/disable code, avoid accumulation of timing error due to trying to maintain remaining-time instead of absolute-end-time, disable timeout before commit not after.
-
- 25 10月, 2002 1 次提交
-
-
由 Tom Lane 提交于
field is signed. Clean up casting.
-
- 20 10月, 2002 1 次提交
-
-
由 Tom Lane 提交于
all utility statement types *except* a short list, per discussion a few days ago. Add missing SetQuerySnapshot calls in VACUUM and REINDEX, and guard against calling REINDEX DATABASE from a function (has same problem as VACUUM).
-
- 19 10月, 2002 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 15 10月, 2002 2 次提交
-
-
由 Tom Lane 提交于
command status at the interactive level. SPI_processed, etc are set in the same way as the returned command status would have been set if the same querystring were issued interactively. Per gripe from Michael Paesold 25-Sep-02.
-
由 Tom Lane 提交于
as per recent pghackers discussions. initdb forced due to change in fields of stored Query nodes.
-
- 14 10月, 2002 1 次提交
-
-
由 Tom Lane 提交于
-
- 09 10月, 2002 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
into postgres.c; make sure it happens for all cases that seem to need it. Perhaps it would be better to explicitly exclude just a few utility statement types from setting a snapshot?
-
- 06 10月, 2002 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 27 9月, 2002 2 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
at this area in the code.
-
- 26 9月, 2002 2 次提交
-
-
由 Bruce Momjian 提交于
handling in the backend.
-
由 Tom Lane 提交于
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.
-
- 20 9月, 2002 1 次提交
-
-
由 Bruce Momjian 提交于
> moment, but they used to be used; I think the correct response is to > put back the missing counter increments, not rip out the counters. Ok, fair enough. It's worth noting that they've been broken for a while -- for example, the HashJoin counter increments were broken when you comitted r1.20 of executor/nodeHashJoin.c in May of '99. I've attached a revised patch that doesn't remove the counters (but doesn't increment them either: I'm not sure of all the places where the counter should be incremented). Neil Conway
-
- 16 9月, 2002 1 次提交
-
-
由 Tom Lane 提交于
(notify/SI-overrun interrupt) while it is in process of doing proc_exit, it is possible for Async_NotifyHandler() to try to start a transaction when one is already running. This leads to Asserts() or worse. I think it may only be possible to occur when frontend synchronization is lost (ie, the elog(FATAL) in SocketBackend() fires), but that is a standard occurrence after error during COPY. In any case, I have seen this failure occur during regression tests, so it is definitely possible.
-
- 05 9月, 2002 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 02 9月, 2002 3 次提交
-
-
由 Bruce Momjian 提交于
pgmonitor. Now log_min_error_statement uses it.
-
由 Bruce Momjian 提交于
because c.h has sys/types.h.
-
由 Bruce Momjian 提交于
Rename debug_print_query to log_statement and rename show_query_stats to show_statement_stats.
-
- 31 8月, 2002 1 次提交
-
-
由 Tom Lane 提交于
to false provides more SQL-spec-compliant behavior than we had before. I am not sure that setting it false is actually a good idea yet; there is a lot of client-side code that will probably be broken by turning autocommit off. But it's a start. Loosely based on a patch by David Van Wie.
-