postgres

Commit Graph

Author	SHA1	Message	Date
Tom Lane	ecc8c3652e	In child-crashed log messages, identify a checkpoint process as such instead of calling it a 'server process'.	23 years ago
Tom Lane	8d86a96068	Adjust CreateCheckpoint so that buffer dumping activities and cleanup of dead xlog segments are not considered part of a critical section. It is not necessary to force a database-wide panic if we get a failure in these operations. Per recent trouble reports.	23 years ago
Bruce Momjian	199f24e19d	More crypt() cleanup.	23 years ago
Bruce Momjian	37627eb571	Remove HPUX 9 rint() test. Cleanup new crypt() source code.	23 years ago
Bruce Momjian	cb8b1299a3	Add Makefile rules for new crypt/rint() /port functions. Add include for rint prototype.	23 years ago
Tom Lane	ba1e066e46	Implement array_send/array_recv (binary I/O for arrays). This exposed the folly of not passing element type to typsend/typreceive, so fix that.	23 years ago
Tom Lane	b1ee615a7f	COPY BINARY uses the new binary I/O routines. Update a few more datatypes so that COPY BINARY regression test passes.	23 years ago
Tom Lane	38d9919d1a	Now that fastpath protocol allows null arguments to be passed, fastpath.c had better check for strict functions.	23 years ago
Tom Lane	0ac6298bb8	Implement new-protocol binary I/O support in DataRow, Bind, and FunctionCall messages. Binary I/O is now up and working, but only for a small set of datatypes (integers, text, bytea).	23 years ago
Bruce Momjian	d85a0a6bef	More cleanups now that we have crypt().	23 years ago
Bruce Momjian	384bbdd0e1	autoconf run for crypt().	23 years ago
Bruce Momjian	66e0a8cb39	Add crypt() to /port for Win32.	23 years ago
Bruce Momjian	89eae96b2f	Remove rint() prototype from QNX.	23 years ago
Bruce Momjian	3afb84cd0f	Remove another old rint() replacement.	23 years ago
Bruce Momjian	0afe5417d7	Add rint() to /port, remove from qnx/.	23 years ago
Bruce Momjian	995773be1c	Pass canAcceptConnections to exec'ed backend, for Jan.	23 years ago
Tom Lane	5ecd4e3f30	Binary send/receive routines for a few basic datatypes --- enough for testing purposes.	23 years ago
Bruce Momjian	4207d6bf30	Add opendir/readdir/closedir() for Win32. Keep SRA copyright on file because it contains BSD license clause.	23 years ago
Tom Lane	45d04099df	Reinstate pg_type's typsend and typreceive columns. They don't do much yet, but they're there. Also some editorial work on CREATE TYPE reference page.	23 years ago
Bruce Momjian	f2c7a27635	Write non-defaults file before signalling the children to reread it.	23 years ago
Bruce Momjian	789a5b340c	Move attached to shared memory out into a separate function for clarity.	23 years ago
Tom Lane	075a0078df	I think we're done with protocol instability, so mark server and libpq as speaking the one true 3.0 protocol.	23 years ago
Tom Lane	c0a8c3ac13	Update 3.0 protocol support to match recent agreements about how to handle multiple 'formats' for data I/O. Restructure CommandDest and DestReceiver stuff one more time (it's finally starting to look a bit clean though). Code now matches latest 3.0 protocol document as far as message formats go --- but there is no support for binary I/O yet.	23 years ago
Bruce Momjian	5e7a5c9511	Pass shared memory address on command line to exec'ed backend. Allow backends to attached to specified shared memory address.	23 years ago
Tom Lane	4e08d35e7d	Fix documentation problem pointed out by Barry Lind: code expected a terminating zero byte in StartupMessage, docs didn't mention it.	23 years ago
Tom Lane	1718f4c66c	Update COPY BINARY file format spec to reflect recent decisions about external representation of binary data.	23 years ago
Tom Lane	2de6da832f	Revise protocol doc for recently-agreed modifications. This is the first version of the 3.0 protocol that can be considered non-draft.	23 years ago
Bruce Momjian	07d35e4277	Change alternate database location patch to test for symlink() rather than WIN32.	23 years ago
Tom Lane	6165a278e5	Fix erroneous example, per Tim Knowles.	23 years ago
Barry Lind	137b123fc7	Fixed bug with Warnings. Warnings are not added to the Statement instead of the connection when appropriate. This checkin also adds the type map for jdbc3, however currently it is identical to the jdbc2 mapping. Modified Files: jdbc/org/postgresql/core/BaseStatement.java jdbc/org/postgresql/core/QueryExecutor.java jdbc/org/postgresql/jdbc3/AbstractJdbc3Connection.java	23 years ago
Bruce Momjian	d9fd7d12f6	Pass shared memory id and socket descriptor number on command line for fork/exec.	23 years ago
Bruce Momjian	e8f4f2f92d	Properly test for buggy flex 2.5.3.	23 years ago
Tom Lane	efa58e105d	Minor editorializing.	23 years ago
Tom Lane	755d191700	Add display of eventual result RowDescription (if any) to the output of Describe on a prepared statement. This was in the original 3.0 protocol proposal, but I took it out for reasons that seemed good at the time. Put it back per yesterday's pghackers discussion.	23 years ago
Tom Lane	8f6a6b7e9a	Ensure that an Execute operation can't send tuples in cases where Describe would claim that no tuples will be returned. Only affects SELECTs added to non-SELECT base queries by rewrite rules. If you want to see the output of such a select, you gotta use 'simple Query' protocol.	23 years ago
Tom Lane	79913910d4	Restructure command destination handling so that we pass around DestReceiver pointers instead of just CommandDest values. The DestReceiver is made at the point where the destination is selected, rather than deep inside the executor. This cleans up the original kluge implementation of tstoreReceiver.c, and makes it easy to support retrieving results from utility statements inside portals. Thus, you can now do fun things like Bind and Execute a FETCH or EXPLAIN command, and it'll all work as expected (e.g., you can Describe the portal, or use Execute's count parameter to suspend the output partway through). Implementation involves stuffing the utility command's output into a Tuplestore, which would be kind of annoying for huge output sets, but should be quite acceptable for typical uses of utility commands.	23 years ago
Michael Meskes	299fbb4b37	Added rfmtlong compatibility function.	23 years ago
Bruce Momjian	3ad406bbc9	Rename internal variables DBName\|dbName to dbname, for consistency.	23 years ago
Bruce Momjian	77a0219ab1	Comment out some of the conditional tests until we have exec(). Reorder non-default variable loading until PGDATA is defined.	23 years ago
Tom Lane	2cf57c8f8d	Implement feature of new FE/BE protocol whereby RowDescription identifies the column by table OID and column number, if it's a simple column reference. Along the way, get rid of reskey/reskeyop fields in Resdoms. Turns out that representation was not convenient for either the planner or the executor; we can make the planner deliver exactly what the executor wants with no more effort. initdb forced due to change in stored rule representation.	23 years ago
Tom Lane	94a3c60324	Ditch ExecGetTupType() in favor of the much simpler ExecGetResultType(), which does the same thing. Perhaps at one time there was a reason to allow plan nodes to store their result types in different places, but AFAICT that's been unnecessary for a good while.	23 years ago
Tom Lane	20aea2ec7b	Alter plpgsql's lexer so that yylineno and yymore are not used. This avoids 'input buffer overflow' failure on long literals, improves performance, gives the right answer for line position in functions containing multiline literals, suppresses annoying compiler warnings, and generally is so much better I wonder why we didn't do it before.	23 years ago
Tom Lane	ea7896bf58	Provide a real link to CREATE SEQUENCE's reference page in nextval/setval discussion.	23 years ago
Tom Lane	e3ed942e3b	Not sure why parser() was still doing clearerr(stdin) ... but it's got to be pointless.	23 years ago
Tom Lane	16503e6fa4	Extended query protocol: parse, bind, execute, describe FE/BE messages. Only lightly tested as yet, since libpq doesn't know anything about 'em.	23 years ago
Bruce Momjian	a59793f82c	Disable alternate locations on Win32 because it doesn't support symlinks.	23 years ago
Tom Lane	50ed78b805	Allow 60 in seconds fields of timestamp, time, interval input values. Per recent discussion on pgsql-general, this is appropriate for spec compliance, and has the nice side-effect of easing porting from old pg_dump files that exhibit the 59.999=>60.000 roundoff problem.	23 years ago
Peter Eisentraut	d1b4327d02	Last round of reference page editing.	23 years ago
Tom Lane	ac5fdea687	When a TIMESTAMP, TIME, or INTERVAL precision is specified larger than our implementation limits, do not issue an ERROR; instead issue a NOTICE and use the max supported value. Per pgsql-general discussion of 28-Apr, this is needed to allow easy porting from pre-7.3 releases where the limits were higher. Unrelated change in same area: accept GLOBAL TEMP/TEMPORARY as a synonym for TEMPORARY, as per pgsql-hackers discussion of 15-Apr. We previously rejected it, but that was based on a misreading of the spec --- SQL92's GLOBAL temp tables are really closer to what we have than their LOCAL ones.	23 years ago
Tom Lane	228697179a	Fix erroneous space calculation leading to core dump in dumpProcLangs, per report from Olivier Prenant. Also fix off-by-one space calculation in ReadToc; this woould not have hurt us until we had more than 100 dependencies for a single object, but wrong is wrong.	23 years ago

1 2 3 4 5 ...

15052 Commits (ecc8c3652e80e7f444e7abb71206b7381cd1b606) All Branches Search

15052 Commits (ecc8c3652e80e7f444e7abb71206b7381cd1b606)

All Branches