aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Clean up various to-do items associated with system indexes:Tom Lane2001-06-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | pg_database now has unique indexes on oid and on datname. pg_shadow now has unique indexes on usename and on usesysid. pg_am now has unique index on oid. pg_opclass now has unique index on oid. pg_amproc now has unique index on amid+amopclaid+amprocnum. Remove pg_rewrite's unnecessary index on oid, delete unused RULEOID syscache. Remove index on pg_listener and associated syscache for performance reasons (caching rows that are certain to change before you need 'em again is rather pointless). Change pg_attrdef's nonunique index on adrelid into a unique index on adrelid+adnum. Fix various incorrect settings of pg_class.relisshared, make that the primary reference point for whether a relation is shared or not. IsSharedSystemRelationName() is now only consulted to initialize relisshared during initial creation of tables and indexes. In theory we might now support shared user relations, though it's not clear how one would get entries for them into pg_class &etc of multiple databases. Fix recently reported bug that pg_attribute rows created for an index all have the same OID. (Proof that non-unique OID doesn't matter unless it's actually used to do lookups ;-)) There's no need to treat pg_trigger, pg_attrdef, pg_relcheck as bootstrap relations. Convert them into plain system catalogs without hardwired entries in pg_class and friends. Unify global.bki and template1.bki into a single init script postgres.bki, since the alleged distinction between them was misleading and pointless. Not to mention that it didn't work for setting up indexes on shared system relations. Rationalize locking of pg_shadow, pg_group, pg_attrdef (no need to use AccessExclusiveLock where ExclusiveLock or even RowExclusiveLock will do). Also, hold locks until transaction commit where necessary.
* The attached patch enables PostgreSQL CVS to build cleanly under CygwinBruce Momjian2001-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | when built against readline 4.2. Specifically, it handles the deprecation of filename_completion_function() with preference for rl_filename_completion_function() Although, I was motivated by Cygwin support, IMO this patch is appropriate for all platforms. To quote from the readline source: #if 0 /* Backwards compatibility (compat.c). These will go away sometime. */ ... extern READLINE_EXPORT(char, *filename_completion_function) ... #endif Note that this patch is modeled after the one by Peter Eisentraut for completion_matches(): http://www.ca.postgresql.org/~petere/readline42.html I tested this patch under the following environments: Cygwin with readline 4.1 Cygwin with readline 4.2 Linux with readline 2.2.1 Linux with readline 4.2 and it behaved as expected. Jason Tishler
* Got two patches that were found by folks on the Castor list, that we'd like toBruce Momjian2001-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | submit. These were done for the jdbc2 driver. The first one is for support of the Types.BIT in the PreparedStatement class. The following lines need to be inserted in the switch statment, at around line 530: (Prepared statment, line 554, before the default: switch case Types.BIT: if (x instanceof Boolean) { set(parameterIndex, ((Boolean)x).booleanValue() ? "TRUE" : "FALSE"); } else { throw new PSQLException("postgresql.prep.type"); } break; The second one is dealing with blobs, inserted in PreparedStatemant.java (After previous patch line, 558): case Types.BINARY: case Types.VARBINARY: setObject(parameterIndex,x); break; and in ResultSet.java (Around line 857): case Types.BINARY: case Types.VARBINARY: return getBytes(columnIndex); Ned Wolpert <ned.wolpert@knowledgenet.com>
* Add French psql translation. (My rendition of French anyway...)Peter Eisentraut2001-06-11
| | | | Fix typo in message.
* Nest macros with slightly less enthusiasm, for performance and to avoidTom Lane2001-06-11
| | | | having non-gcc compilers spit up.
* Move temporary files into 'pg_tempfiles' subdirectory of each databaseTom Lane2001-06-11
| | | | | | directory (which can be made a symlink to put temp files on another disk). Add code to delete leftover temp files during postmaster startup. Bruce, with some kibitzing from Tom.
* Make planner compute the number of hash buckets the same way thatTom Lane2001-06-11
| | | | nodeHash.c will compute it (by sharing code).
* Mark inet,cidr,macaddr '=' operators as mergejoinable.Tom Lane2001-06-10
|
* Fix thinko in hash cost estimation: average frequencyTom Lane2001-06-10
| | | | | | should be computed from total number of distinct values in whole relation, not # distinct values we expect to have after restriction clauses are applied.
* Allow GRANT/REVOKE to/from more than one user per invocation. Command tagPeter Eisentraut2001-06-09
| | | | | | | | for GRANT/REVOKE is now just that, not "CHANGE". On the way, migrate some of the aclitem internal representation away from the parser and build a real parse tree instead. Also add some 'const' qualifiers.
* Teach convert_to_scalar about datatypes timetz, inet, cidr, macaddr.Tom Lane2001-06-09
|
* Add #define for OID of type macaddr.Tom Lane2001-06-09
|
* Remove RelationGetBufferWithBuffer(), which is horribly confused aboutTom Lane2001-06-09
| | | | | | | | | appropriate pin-count manipulation, and instead use ReleaseAndReadBuffer. Make use of the fact that the passed-in buffer (if there is one) must be pinned to avoid grabbing the bufmgr spinlock when we are able to return this same buffer. Eliminate unnecessary 'previous tuple' and 'next tuple' fields of HeapScanDesc and IndexScanDesc, thereby removing a whole lot of bookkeeping from heap_getnext() and related routines.
* Fix a few missed NOIND usages.Tom Lane2001-06-09
|
* Finish German translation, edit (original) messages a bit.Peter Eisentraut2001-06-08
|
* Preliminary code cleanup in elog(). Split out some code into utilityPeter Eisentraut2001-06-08
| | | | | functions, remove indent support, make sure all strings are marked translatable.
* Document and work around ANT bug that prevents directory deletion.Bruce Momjian2001-06-07
|
* reset all: command line and .conf options change defaultsBruce Momjian2001-06-07
| | | | | | | | | | on RESET ALL those are restored. show all: GUC + non-GUC. SHOW ALL, RESET ALL Marko Kreen
* I have ported another Python Postgres interface to Windows (PgSQL). It seemsBruce Momjian2001-06-07
| | | | | | | | | that not many people actually use libpq on Win32; I have found another bug. Some functions that are defined in libpq-fe.h aren't exported in the DLL version of the library. I have added them to src/interfaces/libpq/libpqdll.def. The new complete file is attached. Gerhard H?ring
* This adds unary plus capability. No grammar changes, per Tom's request.Bruce Momjian2001-06-07
| | | | Marko Kreen
* get_seq_name should truncate name to NAMEDATALEN, so that this works:Tom Lane2001-06-06
| | | | | create sequence a1234567890123456789012345678901234567890; select nextval('a1234567890123456789012345678901234567890');
* Be a little smarter about deciding how many most-common values to save.Tom Lane2001-06-06
|
* Add large object finalization cleanup to the proper java file.Bruce Momjian2001-06-06
|
* Remove large object finalize code. Compile error.Bruce Momjian2001-06-06
|
* pgindent fix for asterisk indented too much in return type, for Tom.Bruce Momjian2001-06-06
|
* Patch from Ian Lance Taylor fixing multiple cursor argumentsJan Wieck2001-06-06
| | | | | | and buffer zero termination. Jan
* Adjust WAL code so that checkpoints truncate the xlog at the previousTom Lane2001-06-06
| | | | | | | | | | | | checkpoint's redo pointer, not its undo pointer, per discussion in pghackers a few days ago. No point in hanging onto undo information until we have the ability to do something with it --- and this solves a rather large problem with log space for long-running transactions. Also, change all calls of write() to detect the case where write returned a count less than requested, but failed to set errno. Presume that this situation indicates ENOSPC, and give the appropriate error message, rather than a random message associated with the previous value of errno.
* Correct permissions-checking bugs associated with ancient decision toTom Lane2001-06-05
| | | | | | copy PUBLIC access rights into each newly created ACL entry. Instead treat each ACL entry as independent flags. Also clean up some ugliness in acl.h API.
* Improve planning of OR indexscan plans: for quals likeTom Lane2001-06-05
| | | | | | | | WHERE (a = 1 or a = 2) and b = 42 and an index on (a,b), include the clause b = 42 in the indexquals generated for each arm of the OR clause. Essentially this is an index- driven conversion from CNF to DNF. Implementation is a bit klugy, but better than not exploiting the extra quals at all ...
* Further work on making use of new statistics in planner. Adjust APIsTom Lane2001-06-05
| | | | | | | | | of costsize.c routines to pass Query root, so that costsize can figure more things out by itself and not be so dependent on its callers to tell it everything it needs to know. Use selectivity of hash or merge clause to estimate number of tuples processed internally in these joins (this is more useful than it would've been before, since eqjoinsel is somewhat more accurate than before).
* This patch adds support for %TYPE in CREATE FUNCTION argument and returnBruce Momjian2001-06-04
| | | | | | | types. This version has an elog() to remind the user the type resolution is not dynamic. Ian Lance Taylor
* protected void finalize() {Bruce Momjian2001-06-04
| | | | | | | | | | close(); } in LargeObject.java so that the db resources are released when it is garbage collected or am I missing something? Philip Crotwell
* Give error message, rather than coredump, for utility statements inTom Lane2001-06-04
| | | | | | | conditional rules (rules with WHERE clauses). We cannot support these since there's noplace to hang a condition on a utility statement. We caught the other case (attempt to attach a condition at rewrite time) awhile ago, but this one escaped notice until now.
* Mark many strings in backend not covered by elog for translation. Also,Peter Eisentraut2001-06-03
| | | | make strings in xlog.c look more like English and less like binary noise.
* Accept and output '-Infinity' as well as 'Infinity', per long-agoTom Lane2001-06-02
| | | | | suggestion from Ross Reedstrom. Still needs work to make those symbols convert to actual IEEE infinities (on machines where such things exist).
* Tweak sorting so that nulls appear at the front of a descending sortTom Lane2001-06-02
| | | | | | | | | | | (vs. at the end of a normal sort). This ensures that explicit sorts yield the same ordering as a btree index scan. To be really sure that that equivalence holds, we use the btree entries in pg_amop to decide whether we are looking at a '<' or '>' operator. For a sort operator that has no btree association, we put the nulls at the front if the operator is named '>' ... pretty grotty, but it does the right thing in simple ASC and DESC cases, and at least there's no possibility of getting a different answer depending on the plan type chosen.
* Native Language Support (NLS)Peter Eisentraut2001-06-02
| | | | | | | | | | | Use --enable-nls to turn it on; see installation instructions for details. See developer's guide how to make use of it in programs and how to add translations. psql sources have been almost fully prepared and an incomplete German translation has been provided. In the backend, only elog() calls are currently translatable, and the provided German translation file is more of a placeholder.
* Paranoia about unordered comparisons in IEEE float math. If we areTom Lane2001-06-02
| | | | | | given values that compare as unordered, make sure we reply that they are equal, which is better than giving an arbitrary answer --- at least it doesn't depend on which one is passed as which arg.
* dllist.c is included in the frontend libpq interface via symlink.Jan Wieck2001-06-02
| | | | | | | There is no elog() available. Used fprintf(stderr, ...) and exit instead. Jan
* The following patch for JDBC fixes an issue with jdbc running on aBruce Momjian2001-06-01
| | | | | | | | non-multibyte database loosing 8bit characters. This patch will cause the jdbc driver to ignore the encoding reported by the database when multibyte isn't enabled and use the JVM default in that case. Barry Lind
* Check for malloc failure.Tom Lane2001-06-01
|
* Guard against malloc failure. Also, don't examine segP->lastBackendTom Lane2001-06-01
| | | | until we hold the spinlock.
* Check for malloc failure.Tom Lane2001-06-01
|
* If spi.c wants to use malloc, it better test for malloc failure.Tom Lane2001-06-01
|
* pltcl, plperl, and plpython all suffer the same bug previously fixedTom Lane2001-06-01
| | | | | | | | in plpgsql: they fail for datatypes that have old-style I/O functions due to caching FmgrInfo structs with wrong fn_mcxt lifetime. Although the plpython fix seems straightforward, I can't check it here since I don't have Python installed --- would someone check it?
* New improved version of bpcharin() may have got the truncation caseTom Lane2001-06-01
| | | | | | | | | right, but it failed to get the padding case right. This was obscured by subsequent application of bpchar() in all but one regression test case, and that one didn't fail in an obvious way --- trailing blanks are hard to see. Add another test case to make it more obvious if it breaks again.
* Fix for:Bruce Momjian2001-06-01
| | | | | | | | > Example form two pg_dump outputs > 7.1.2 : > COPY "list" FROM stdin; > 7.0.2 : > COPY "list" FROM stdin;
* Remove fastpath.c's lame attempt at caching function lookup info acrossTom Lane2001-06-01
| | | | | | | | | calls. This has never actually cached anything, because postgres.c does each fastpath call as a separate transaction command, and so fastpath.c would always decide that its cache was outdated. If it had worked, it would now be failing for calls of oldstyle functions due to dangling pointers in the FmgrInfo struct. Rip it out for simplicity and bug- proofing.
* - Synced preproc.y with gram.y.Michael Meskes2001-06-01
| | | | | | | - Synced pgc.l with scan.l. - Synced keyword.c. - Set ecpg version to 2.9.0. - Set library version to 3.3.0.
* Clean up some minor problems exposed by further thought about Panon's bugTom Lane2001-06-01
| | | | | | | | | | | | | | report on old-style functions invoked by RI triggers. We had a number of other places that were being sloppy about which memory context FmgrInfo subsidiary data will be allocated in. Turns out none of them actually cause a problem in 7.1, but this is for arcane reasons such as the fact that old-style triggers aren't supported anyway. To avoid getting burnt later, I've restructured the trigger support so that we don't keep trigger FmgrInfo structs in relcache memory. Some other related cleanups too: it's not really necessary to call fmgr_info at all while setting up the index support info in relcache entries, because those ScanKeyEntry structs are never used to invoke the functions. This should speed up relcache initialization a tiny bit.
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-15 14:24:33 +0000