summaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAgeFilesLines
* Attempting to insert a value of 'now' into a datetime typeBruce Momjian1999-03-141-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | results in a bogus datetime value under AlphaLinux. (Note that the link to submit a port-specific bug on your website is broken) -Test Case: ---------- testdb=> create table dttest (dt datetime); testdb=> insert into dttest values ('now'); -------------------------------------------------------------------------- Solution: --------- The basic problem is the typedefs of AbsoluteTime and RelativeTime, which are both 'int32'. These types appear to be used synonymously with the 'time_t' type, which on AlphaLinux is typedef'd as a 'long int', which is 64-bits (not 32). The solution included here fixes the datetime type (it now passes the regression test), but does not pass the absolute and relative time regression tests. Presumably, a more thorough investigation of how these types are used is warranted. The included patch is from the v6.3.2 source, but can be applied to the v6.4.2 source. Please note that there is also a RedHat-specific patch distributed with the PostgreSQL source package from RedHat that was applied first. Rich Edwards
* Here is a little syntax error found in a .y file... A dropped semi.Bruce Momjian1999-03-141-9/+1
| | | | | | DwD -- Daryl W. Dunbar
* Cleanup of hash functions in pg_proc.Bruce Momjian1999-03-141-3650/+3640
|
* compile cleanupBruce Momjian1999-03-141-2/+3
|
* Compile cleanupBruce Momjian1999-03-141-2/+2
|
* Done.Bruce Momjian1999-03-141-15/+32
| | | | | | | o overwriting an existing lobj now works o 8KB garbage block always inserted problem is fixed Tatsuo Ishii
* I've been having also sorts of fun trying to get kerberos 4Bruce Momjian1999-03-141-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | authentifica tion working with postgresql-6.4.2 and KTH-KRB Ebones (http://www.pdc.kth.se/kth-kr b) on a dec alpha running DU 4.0D using the native compiler. The following patch does the trick. The rationale behind this is as follows. The KTH-KRB code header files defines lots of lengths like INST_SZ,REALM_SZ and KRB_SENDAUTH_VLEN. It also has a habit of doing things like chararray[LENGTH] = '\0' to ensure null terminated strings. In my instance this just happens to blat the kerberos principal instance string leading to error like pg_krb4_recvauth: kerberos error: Can't decode authenticator (krb_rd_req ) The application code that comes with KTH-KRB uses "KRB_SENDAUTH_VLEN + 1" and sometimes uses "INST_SZ + 1" so it seems safest to put that 1 char buffer in the appropriate place. Rodney McDuff
* We have tested the patches on three platforms:Bruce Momjian1999-03-143-5/+7
| | | | | | | | | | | | | NetBSD/macppc LinuxPPC FreeBSD 2.2.6-RELEASE All of them seem happy with the regression test. Note that, however, compiling with optimization enabled on NetBSD/macppc causes an initdb failure (other two platforms are ok). After checking the asm code, we are suspecting that might be a compiler(egcs) bug. Tatsuo Ishii
* Hello,Bruce Momjian1999-03-141-1/+4
| | | | | | | | | I've been working on the following TODO list item: * psql \d on index with char()/varchar() fields shows improper length I've attached a simple patch to fix this. -Ryan
* I have a problem with Access97 not working properly when entering newBruce Momjian1999-03-142-2/+4
| | | | | | | | | | | | | | records using a sub form, i.e. entering a new order/orderlines or master and detail tables. The problem is caused by a SQL statement that Access97 makes involving NULL. The syntax that fails is "column_name" = NULL. The following attachment was provided by -Jose'-. It contains a very small enhancement to gram.y that will allow Access97 to work properly with sub forms. Can this enhancement be added to release 6.5? <<gram.patch>> Thanks, Michael
* Enclosed below I have a patch to allow a btree index on the int8 type.Bruce Momjian1999-03-142-2/+19
| | | | | | | | | | | | | | | I would like some feedback on what the hash function for the int8 hash function in the ./backend/access/hash/hashfunc.c should return. Also, could someone (maybe Tomas Lockhart?) look-over the patch and make sure the system table entries are correct? I've tried to research them as much as I could, but some of them are still not clear to me. Thanks, -Ryan
* We have to return dummy tuple for empty targetlist!Vadim B. Mikheev1999-03-101-9/+8
| | | | | | Try select t1.x from t1, t2 where t1.y = 1 and t2.y = 1 - t2 scan target list will be empty and so no one tuple will be returned...
* Changes to fix/improve the dynamic loading on NTMarc G. Fournier1999-03-092-5/+5
| | | | From: Horak Daniel <horak@mmp.plzen-city.cz>
* Fix OR index selectivity problem.Bruce Momjian1999-03-082-27/+19
|
* Fix for Alpha OR selectivity bug.Bruce Momjian1999-03-081-2/+2
|
* Export include/utils/mcxt.h so that external stuff can includeTom Lane1999-03-071-12/+74
| | | | | | palloc.h again. Move exporting of backend header files out of libpq's Makefile (whatever was it doing there in the first place?) and into backend/Makefile.
* Modify mcxt.h so that it doesn't pull in half of creation.Tom Lane1999-03-071-1/+2
|
* Really remove Recipe.Bruce Momjian1999-03-073-5185/+5137
|
* A few further tweaks to shared memory space estimation.Tom Lane1999-03-064-24/+35
| | | | | This change brings the default size of the main shmem block back under 1MB, which is a fairly popular value for the kernel's SHMMAX parameter.
* Partial fix for copied-plan bugs reported by Hiroshi Inoue:Tom Lane1999-03-032-10/+15
| | | | | | | _copyResult didn't copy subPlan structure completely. _copyAgg is still busted, apparently because of changes from EXCEPT/INTERSECT patch (get_agg_tlist_references is no longer sufficient to find all aggregates). No time to look at that tonight, however.
* Executor no longer cares about mergejoinop, mergerightorder, mergeleftorder,Tom Lane1999-03-017-88/+97
| | | | | | | | | so remove them from MergeJoin node. Hack together a partial solution for commuted mergejoin operators --- yesterday a mergejoin int4 = int8 would crash if the planner decided to commute it, today it works. The planner's representation of mergejoins really needs a rewrite though. Also, further testing of mergejoin ops in opr_sanity regress test.
* Fix executor to work correctly with mergejoins where left andTom Lane1999-02-281-118/+75
| | | | right sides have different data types.
* Remove recipe.o from Makefile ... dead code not quite dead enough,Tom Lane1999-02-271-2/+2
| | | | it seems.
* Someone forgot to commit gram.c and parse.h after his latestTom Lane1999-02-272-3729/+3686
| | | | set of updates to gram.y.
* Remove reference to recipe.h.Bruce Momjian1999-02-251-2/+1
|
* Fix problem with selectivity error in added columns with ALTER TABLE.Bruce Momjian1999-02-246-7/+28
| | | | Move files to deadcode.
* update commentsBruce Momjian1999-02-241-78/+89
|
* Thank you for the advice. I concluded that current inet code has aBruce Momjian1999-02-241-2/+7
| | | | | | | | portability problem. Included patches should be applied to both current and 6.4 tree. I have tested on LinuxPPC, FreeBSD and Solaris 2.6. Now the inet regression tests on these platforms are all happy. --- Tatsuo Ishii
* Add a few other parser-only nodes for debugging help.Thomas G. Lockhart1999-02-231-22/+32
| | | | Define the JoinExpr node.
* Clean up error messages.Thomas G. Lockhart1999-02-233-33/+33
|
* Do a better job of selecting candidates among functionsThomas G. Lockhart1999-02-231-47/+48
| | | | | when no exact match. Clean up elog error messages.
* Include some new code for outer joins. Disabled by default, but enable byThomas G. Lockhart1999-02-231-20/+222
| | | | | including the following in your Makefile.custom: CFLAGS+= -DENABLE_OUTER_JOINS -DEXEC_MERGEJOINDEBUG
* Put in explicit checks for implicit index name lengths.Thomas G. Lockhart1999-02-231-15/+54
| | | | | Put in hooks for outer joins by passing a few parameters back and forth in function calls. May not be close to working yet.
* Modify the outer join placeholder code with something closer to workingThomas G. Lockhart1999-02-231-118/+160
| | | | code. Works here, but not completely implemented past this point.
* Fix typos in comments.Thomas G. Lockhart1999-02-231-3/+3
|
* Add first code to help with outer joins.Thomas G. Lockhart1999-02-231-120/+247
| | | | | | Enable by defining CFLAGS+= -DENABLE_OUTER_JOINS -DEXEC_MERGEJOINDEBUG in your Makefile.custom
* Fix typo in comment.Thomas G. Lockhart1999-02-231-2/+2
|
* Rearrange order of subdirectory creation to help generate parse.hThomas G. Lockhart1999-02-232-6/+11
| | | | | | | | file early enough to use in nodes/. Try to be more complete for rules on generating parse.h, but it still does not work any better than before. Should be able to make correctly if parser/gram.y is updated even without a "make clean" but so far not there yet.
* comments cleanup.Bruce Momjian1999-02-223-25/+16
|
* comment cleanup.Bruce Momjian1999-02-223-299/+190
|
* ifdef out append().Bruce Momjian1999-02-221-1/+3
|
* Ok. I found an align problem in lobj that might not appear other thanBruce Momjian1999-02-221-2/+3
| | | | | | | Solaris/sparc. Please apply included patches to src/backend/storage/large_object/inv_api.c and try again. (These are Tatsuo Ishii
* Repair some pretty serious problems in dynahash.c andTom Lane1999-02-226-158/+160
| | | | | | shared memory space allocation. It's a wonder we have not seen bug reports traceable to this area ... it's quite clear that the routine dir_realloc() has never worked correctly, for example.
* more cleanupBruce Momjian1999-02-222-7/+80
|
* Final optimizer cleanups.Bruce Momjian1999-02-2212-138/+153
|
* fix compile problem.Bruce Momjian1999-02-221-2/+2
|
* From: Tatsuo Ishii <t-ishii@sra.co.jp>Marc G. Fournier1999-02-2137-126/+126
| | | | | | Ok. I made patches replacing all of "#if FALSE" or "#if 0" to "#ifdef NOT_USED" for current. I have tested these patches in that the postgres binaries are identical.
* pathkeys.c cleanup.Bruce Momjian1999-02-213-65/+44
|
* Rearrange handling of MAXBACKENDS a little bit. The default settingTom Lane1999-02-215-49/+54
| | | | | | | | | of MAXBACKENDS is now 1024, since all it's costing is about 32 bytes of memory per array slot. configure's --with-maxbackends switch now controls DEF_MAXBACKENDS which is simply the default value of the postmaster's -N switch. Thus, the out-of-the-box configuration will still limit you to 64 backends, but you can go up to 1024 backends simply by restarting the postmaster with a different -N switch --- no rebuild required.
* pathkeys fixesBruce Momjian1999-02-203-21/+53
|