aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* heap_close(rel, AccessShareLock);Vadim B. Mikheev1999-09-28
| | | | ^^^^^^^^^^^^^^^^^ need in
* Addition of CmdTuples(). Wraps PQcmdTuples.Bruce Momjian1999-09-28
| | | | Vince Vielhaber
* I have been working with user defined types and user defined cBruce Momjian1999-09-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | functions. One problem that I have encountered with the function manager is that it does not allow the user to define type conversion functions that convert between user types. For instance if mytype1, mytype2, and mytype3 are three Postgresql user types, and if I wish to define Postgresql conversion functions like I run into problems, because the Postgresql dynamic loader would look for a single link symbol, mytype3, for both pieces of object code. If I just change the name of one of the Postgresql functions (to make the symbols distinct), the automatic type conversion that Postgresql uses, for example, when matching operators to arguments no longer finds the type conversion function. The solution that I propose, and have implemented in the attatched patch extends the CREATE FUNCTION syntax as follows. In the first case above I use the link symbol mytype2_to_mytype3 for the link object that implements the first conversion function, and define the Postgresql operator with the following syntax The patch includes changes to the parser to include the altered syntax, changes to the ProcedureStmt node in nodes/parsenodes.h, changes to commands/define.c to handle the extra information in the AS clause, and changes to utils/fmgr/dfmgr.c that alter the way that the dynamic loader figures out what link symbol to use. I store the string for the link symbol in the prosrc text attribute of the pg_proc table which is currently unused in rows that reference dynamically loaded functions. Bernie Frankpitt
* Reverse out last scan.l patch for minus handling.\Bruce Momjian1999-09-28
|
* Fix nodeAgg coredump in case where lower-level plan hasTom Lane1999-09-28
| | | | | | | an empty targetlist *and* fails to return any tuples, as will happen for example with 'SELECT COUNT(1) FROM table WHERE ...' if the where- clause selects no tuples. It's so nice to make a fix by diking out code, instead of adding more...
* Sorry, guys. Here is the ultimate patch which keeps the entireBruce Momjian1999-09-27
| | | | | | | | | | behavior as it was, apart from forbidding minus-terminated operators. Seems that I have to break the habit of doing before thinking properly :-/ The point is that my second patch breaks constructs like a & b or a ! b. This patch is to be applied instead of any of two other today's patches. Leon
* Irix fix from Mark DalphinBruce Momjian1999-09-27
|
* Massimo's SET FSYNC and SHOW PG_OPTIONS changes, without SET QUERY_LIMIT.Bruce Momjian1999-09-27
|
* Cancel query support from MassimoBruce Momjian1999-09-27
|
* Following advice from Michael Ansley, I broke up the patch inBruce Momjian1999-09-27
| | | | | | | two: one fixes uminus and other literal length. They are to be applied - uminus first, then possilbly literal on top of uminus. Leon
* Hello,Bruce Momjian1999-09-27
| | | | | | | | | | | | | | | | | | Two patches included: - the first one enables the use of bool variables in fields which might become NULL. Up to now the lib told you that NULL is not a bool variable, even if you provide a indicator. - the second patch checks whether a value is null and issues an error if no indicator is provided. Sidenote: IIRC, the variable should be left alone if the value is NULL. ECPGlib sets it's value to 0 on NULL. Is this a violation of the standard? Regards Christof
* Currently,only the first column of multi-column indicesBruce Momjian1999-09-27
| | | | | | | | | | | | | is used to find start scan position of Indexscan-s. To speed up finding scan start position,I have changed _bt_first() to use as many keys as possible. I'll attach the patch here. Regards. Hiroshi Inoue
* Emit warning on SELECT pg_language.*Bruce Momjian1999-09-27
|
* Fix to give super user and createdb user proper update catalog rights.Bruce Momjian1999-09-27
|
* Transaction log manager core code.Vadim B. Mikheev1999-09-27
| | | | It doesn't work currently but also don't break anything -:)
* *** empty log message ***Michael Meskes1999-09-27
|
* Add README.SSLBruce Momjian1999-09-27
|
* Lots of patches coming in from me today :-)Bruce Momjian1999-09-27
| | | | | | | | | | When drawing up a very simple "text-drawing" of how the negotiation is done, I realised I had done this last part (fallback) in a very stupid way. Patch #4 fixes this, and does it in a much better way. Included is also the simple text-drawing of how the negotiation is done. //Magnus
* Add bsdi sparc port.Bruce Momjian1999-09-27
|
* Modify nodeAgg.c so that no rows are returned for a GROUP BYTom Lane1999-09-26
| | | | | | | | with no input rows, per pghackers discussions around 7/22/99. Clean up a bunch of ugly coding while at it; remove redundant re-lookup of aggregate info at start of each new GROUP. Arrange to pfree intermediate values when they are pass-by-ref types, so that aggregates on pass-by-ref types no longer eat memory. This takes care of a couple of TODO items...
* Implement constant-expression simplification per BernardTom Lane1999-09-26
| | | | | | | | | | | Frankpitt, plus some improvements from yours truly. The simplifier depends on the proiscachable field of pg_proc to tell it whether a function is safe to pre-evaluate --- things like nextval() are not, for example. Update pg_proc.h to contain reasonable cacheability information; as of 6.5.* hardly any functions were marked cacheable. I may have erred too far in the other direction; see recent mail to pghackers for more info. This update does not force an initdb, exactly, but you won't see much benefit from the simplifier until you do one.
* This is a patch for cygipc library provided by Yutaka Tanida.Hiroshi Inoue1999-09-24
| | | | This is necessary to prevent freezing in cygwin port.
* Several changes here, not very related but touching some of the same files.Tom Lane1999-09-24
| | | | | | | | | | | | | | | | | | | | | * Buffer refcount cleanup (per my "progress report" to pghackers, 9/22). * Add links to backend PROC structs to sinval's array of per-backend info, and use these links for routines that need to check the state of all backends (rather than the slow, complicated search of the ShmemIndex hashtable that was used before). Add databaseOID to PROC structs. * Use this to implement an interlock that prevents DESTROY DATABASE of a database containing running backends. (It's a little tricky to prevent a concurrently-starting backend from getting in there, since the new backend is not able to lock anything at the time it tries to look up its database in pg_database. My solution is to recheck that the DB is OK at the end of InitPostgres. It may not be a 100% solution, but it's a lot better than no interlock at all...) * In ALTER TABLE RENAME, flush buffers for the relation before doing the rename of the physical files, to ensure we don't get failures later from mdblindwrt(). * Update TRUNCATE patch so that it actually compiles against current sources :-(. You should do "make clean all" after pulling these changes.
* One last missing quoting bug in pg_dump:Bruce Momjian1999-09-23
| | | | | | | | | | | | | | | | | | now that sequence names are properly quoted for field defaults, mixed case sequence names are generated. These are properly quoted in the CREATE SEQUENCE lines, but not in the SELECT nextval lines, as per below: CREATE SEQUENCE "Teams_TeamID_seq" start 10 increment 1 maxvalue 2147483647 minvalue 1 cache 1 ; SELECT nextval ('Teams_TeamID_seq'); This needs to be: SELECT nextval ('"Teams_TeamID_seq"'); Patch included below. -- Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
* Fix for netmask('x.x.x.x/0') is 255.255.255.255 instead of 0.0.0.0Bruce Momjian1999-09-23
| | | | | | This is because (-1) << 32 is -1 (Only intel arc. has been checked) Oleg Sharoiko
* TRUNCATE command from Mike Mascari<mascarim@yahoo.com>Bruce Momjian1999-09-23
|
* Add TRUNCATE command, with psql help and sgml additions.Bruce Momjian1999-09-23
|
* I found the following useful - just a way of using PQgetisnull fromBruce Momjian1999-09-21
| | | | | | libpq++. Patrick Welche
* gram.y cleanupBruce Momjian1999-09-21
|
* values.h patch from Alex HowanskyBruce Momjian1999-09-21
|
* last batch, I think...Marc G. Fournier1999-09-20
|
* fixing it more..Marc G. Fournier1999-09-20
|
* bring it all into -current againMarc G. Fournier1999-09-20
|
* try and fix things...Marc G. Fournier1999-09-20
|
* bring in missing files ... this isn't very clean, but :(Marc G. Fournier1999-09-20
|
* Make proper plpgsql non-externs.Bruce Momjian1999-09-20
|
* Define plpgsql_yylineno as non-extern somewhere for bsdi.Bruce Momjian1999-09-20
|
* Remove incorrect 'Assert(targetList != NULL)'. AnTom Lane1999-09-19
| | | | | INSERT ... DEFAULT VALUES statement does indeed have a null targetlist, at least during parse and rewrite stages.
* Fix CASE bug identified by Keith Parks: CASE didn't reliablyTom Lane1999-09-18
| | | | | treat a NULL condition result as FALSE. Clean up some bogus comments here and there, too.
* Update regress test expected outputs for small changes inTom Lane1999-09-18
| | | | | error message wording, due to most cases of no-such-relation now being detected in central heap_open code rather than on an ad-hoc basis.
* Mega-commit to make heap_open/heap_openr/heap_close take anTom Lane1999-09-18
| | | | | | | | | | | | | | | | | additional argument specifying the kind of lock to acquire/release (or 'NoLock' to do no lock processing). Ensure that all relations are locked with some appropriate lock level before being examined --- this ensures that relevant shared-inval messages have been processed and should prevent problems caused by concurrent VACUUM. Fix several bugs having to do with mismatched increment/decrement of relation ref count and mismatched heap_open/close (which amounts to the same thing). A bogus ref count on a relation doesn't matter much *unless* a SI Inval message happens to arrive at the wrong time, which is probably why we got away with this sloppiness for so long. Repair missing grab of AccessExclusiveLock in DROP TABLE, ALTER/RENAME TABLE, etc, as noted by Hiroshi. Recommend 'make clean all' after pulling this update; I modified the Relation struct layout slightly. Will post further discussion to pghackers list shortly.
* *** empty log message ***Michael Meskes1999-09-17
|
* *** empty log message ***Michael Meskes1999-09-17
|
* Changes made by Hiroshi Inoue and approved by Vadim.Tatsuo Ishii1999-09-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | See attached mail for more details. ------------------------------------------------------------------- From: "Vadim Mikheev" <vadim@krs.ru> To: "Hiroshi Inoue" <Inoue@tpf.co.jp> References: <000201befa94$42fe04c0$2801007e@cadzone.tpf.co.jp> Subject: Re: elog(ERROR) in vacuum Date: Fri, 10 Sep 1999 10:27:10 +0900 Organization: OJSC Rostelecom (Krasnoyarsk) Message-ID: <37D85E6E.5AFA126D@krs.ru> Hiroshi Inoue wrote: > > Hello Vadim, > > I have a question about vacuum. > > VACUUM has a phase like commit which calls TransactionIdCommit(). > But if elog(ERROR) occured after that,the status of transaction is > changed from XID_COMMIT to XID_ABORT. > > Seems to me this causes inconsistency. > Shoudn't AbortTransaction() be changed not to call TransacionIdAbort() > in case of vacuum. You're right! As usual -:) Vadim
* jdbc2real rule was in there twice. One of them should have been jdbc1realPeter Mount1999-09-15
|
* Jens Glaser found that getPrimaryKeys() had a table called test hardwiredPeter Mount1999-09-15
| | | | into it.
* Some late patches from Jens Glaser (jens@jens.de). These upgrade the protocolPeter Mount1999-09-15
| | | | to version 2, and fixes ResultSetMetaData.getColumnDisplaySize().
* *** empty log message ***Michael Meskes1999-09-15
|
* An abstract declaration for the close() method was missed out of the previousPeter Mount1999-09-14
| | | | commit to CVS.
* Allow ISOLATION and LEVEL as column names. These are SQL92 reserved wordsThomas G. Lockhart1999-09-14
| | | | which do not need to be so for our parser. Apparently omitted earlier.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-15 04:07:56 +0000