aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
...
* Fix longstanding bug with VIEW using BETWEEN: OffsetVarNodes would getTom Lane2000-12-21
| | | | | | applied to the duplicated subtree twice. Probably someday we should fix the parser not to generate multiple links to the same subtree, but for now a quick copyObject() is the path of least resistance.
* Remove multi.c and single.c, which have been dead code forTom Lane2000-12-20
| | | | over two years.
* Prevent freshly-started backend from ignoring SIGUSR1, per race conditionTom Lane2000-12-20
| | | | | | | observed by Inoue. Also, don't call ProcRemove() from postmaster if we have detected a backend crash --- too risky if shared memory is corrupted. It's not needed anyway, considering we are going to reinitialize shared memory and semaphores as soon as the last child is dead.
* >> Here is a patch for the beos port (All regression tests are OK).Bruce Momjian2000-12-18
| | | | | | | | | | | | | | | | | | | | | | >> xlog.c : special case for beos to avoid 'link' which does not work yet >> beos/sem.c : implementation of new sem_ctl call (GETPID) and a new >sem_op >> flag (IPCNOWAIT) >> dynloader/beos.c : add a verification of symbol validity (seem that the >> loader sometime return OK with an invalid symbol) >> postmaster.c : add beos forking support for the new checkpoint process >> postgres.c : remove beos special case for getrusage >> beos.h : Correction of a bas definition of AF_UNIX, misc defnitions >> >> >> thanks >> >> >> cyril Cyril VELTER
* Ensure that 'errno' is saved and restored by all signal handlers thatTom Lane2000-12-18
| | | | | | might change it. Experimentation shows that the signal handler call mechanism does not save/restore errno for you, at least not on Linux or HPUX, so this is definitely a real risk.
* Make sure make_rels_by_clause_joins doesn't return multiple referencesTom Lane2000-12-18
| | | | | to same joinrel. Although make_rels_by_joins doesn't mind, GEQO has an Assert that doesn't like this.
* Repair mishandling of PRIMARY KEY declaration that references anTom Lane2000-12-18
| | | | inherited column, per bug report from Elphick 12/15/00.
* Clean up backend-exit-time cleanup behavior. Use on_shmem_exit callbacksTom Lane2000-12-18
| | | | | | to ensure that we have released buffer refcounts and so forth, rather than putting ad-hoc operations before (some of the calls to) proc_exit. Add commentary to discourage future hackers from repeating that mistake.
* Tweak select_common_type() to deal with possibility of multiple preferredTom Lane2000-12-17
| | | | | types in a category --- it was taking the last preferred type among the inputs, rather than the first one as intended.
* Remove current->old mapping.Bruce Momjian2000-12-15
|
* Make algorithm for resolving UNKNOWN function/operator inputs beTom Lane2000-12-15
| | | | insensitive to the order of arguments. Per pghackers discussion 12/10/00.
* here is a patch fixing today's bug report:Bruce Momjian2000-12-15
| | | | | | | | | | | | | | | | | | | | > Date: Thu, 14 Dec 2000 12:44:47 +0100 (CET) > From: Kovacs Zoltan Sandor <tip@pc10.radnoti-szeged.sulinet.hu> > To: pgsql-bugs@postgresql.org > Subject: [BUGS] to_char() causes backend to close connection > > Hi, this query gives different strange results: > > select to_char(now()::abstime,'YYMMDDHH24MI'); > > I get e.g. a "backend closed the channel unexpectedly..." error with > successful or failed resetting attempt (indeterministic) Again thanks Kovacs, you found really designing bug, that appear if anyone write bad format template to "number" version of to_char() (as you with 'DD'). Karel
* Remove obsolete comment.Tom Lane2000-12-15
|
* Remove a few remaining vestiges of elog(WARN).Tom Lane2000-12-15
|
* BugfixJan Wieck2000-12-14
| | | | | | | | Trying to connect to template0 left a global referenced buffer because the scan of pg_database wasn't ended properly before elog(FATAL). Jan
* Planner speedup hacking. Avoid saving useless pathkeys, so that pathTom Lane2000-12-14
| | | | | | | | | | | | comparison does not consider paths different when they differ only in uninteresting aspects of sort order. (We had a special case of this consideration for indexscans already, but generalize it to apply to ordered join paths too.) Be stricter about what is a canonical pathkey to allow faster pathkey comparison. Cache canonical pathkeys and dispersion stats for left and right sides of a RestrictInfo's clause, to avoid repeated computation. Total speedup will depend on number of tables in a query, but I see about 4x speedup of planning phase for a sample seven-table query.
* Make sure to not handle deactivated system indexesHiroshi Inoue2000-12-14
|
* Change StoreCatalogInheritance() to work from a list of parent relationTom Lane2000-12-14
| | | | | | OIDs rather than names. Aside from being simpler and faster, this way doesn't blow up in the face of 'create temp table foo () inherits (foo)'. Which is a rather odd thing to do, but it seems some people want to.
* Fix thinko for case of outer join where inner table is empty: shouldTom Lane2000-12-13
| | | | output first outer tuple before advancing...
* Cache eval cost of qualification expressions in RestrictInfo nodes toTom Lane2000-12-12
| | | | | | | avoid repeated evaluations in cost_qual_eval(). This turns out to save a useful fraction of planning time. No change to external representation of RestrictInfo --- although that node type doesn't appear in stored rules anyway.
* Remove elog for online log files.Vadim B. Mikheev2000-12-11
|
* elog(LOG)-->elog(DEBUG) for skipped logs.Vadim B. Mikheev2000-12-11
|
* Tweak Darwin patch to get right include order.Tom Lane2000-12-11
|
* Resolve complie error(was my fault).Hiroshi Inoue2000-12-11
|
* *redo: Heap move* neglects to set t_cmin for MOVED_IN tuples.Hiroshi Inoue2000-12-11
|
* Fix ILIKE bug (only in multi-byte case)Tatsuo Ishii2000-12-11
|
* Darwin porting patches from Peter Bierman <bierman@apple.com>Tom Lane2000-12-11
|
* Portability fix from Ryan Kirkpatrick's Alpha patches. I believe thisTom Lane2000-12-09
| | | | is the only diff not accounted for by fmgr rewrite...
* Suppress compiler warnings.Tom Lane2000-12-09
|
* Fix a bug in conversion from big5 to EUC_TW (CNS 11643-1992 Plane 3)Tatsuo Ishii2000-12-09
| | | | Thanks Chih-Chang Hsieh <cch@cc.kmu.edu.tw> for finding the bug.
* Repair erroneous use of hashvarlena() for MACADDR, which is not aTom Lane2000-12-08
| | | | | | | varlena type. (I did not force initdb, but you won't see the fix unless you do one.) Also, make sure all index support operators and functions are careful not to leak memory for toasted inputs; I had missed some hash and rtree support ops on this point before.
* Resurrect -F switch: it controls fsyncs again, though the fsyncs areTom Lane2000-12-08
| | | | | mostly just on the WAL logfile nowadays. But if people want to disable fsync for performance, why should we say no?
* Add missing copyright and RCS identification header.Tom Lane2000-12-08
|
* Remove error check that disallowed setval() on a sequence with cacheTom Lane2000-12-08
| | | | | | | | | value greater than one. The behavior this sought to disallow doesn't seem any less confusing than the other behaviors of cached sequences. Improve wording of some error messages, too. Update documentation accordingly. Also add an explanation that aborted transactions do not roll back their nextval() calls; this seems to be a FAQ, so it ought to be mentioned here...
* Cache invalidation for vacuum of system tables.Hiroshi Inoue2000-12-08
|
* REINDEX under WAL.Hiroshi Inoue2000-12-08
|
* Change lpad() and rpad() to behave more Oracle-compatibly when targetTom Lane2000-12-07
| | | | length is less than original string length.
* checkretval() failed to cope with an empty SQL function body.Tom Lane2000-12-07
|
* Make OVERLAPS operators conform to SQL92 spec regarding NULL handling.Tom Lane2000-12-07
| | | | | | | | | | As I read it, the spec requires a non-null result in some cases where one of the inputs is NULL: specifically, if the other endpoint of that interval is between the endpoints of the other interval, then the result is known TRUE despite the missing endpoint. The spec could've been a lot simpler if they did not intend this behavior. I did not force an initdb for this change, but if you don't do one you'll still see the old strict-function behavior.
* RecordTransactionAbort() shouldn't log XLOG_XACT_ABORTHiroshi Inoue2000-12-07
| | | | if the transaction has already been committed ?
* Silence compiler warning.Tom Lane2000-12-07
|
* Silence compiler warning.Tom Lane2000-12-07
|
* Make application of FOR UPDATE to a view work exactly like the parser'sTom Lane2000-12-07
| | | | transformForUpdate does: it should recurse into subqueries.
* transformForUpdate() mustn't assume rowMarks list is initially empty.Tom Lane2000-12-07
| | | | | It could be recursing into a sub-query where there was already a FOR UPDATE clause.
* Clean up handling of FOR UPDATE inside views and subselects ... make itTom Lane2000-12-06
| | | | | | | work where we can (given that the executor only handles it at top level) and generate an error where we can't. Note that while the parser has been allowing views to say SELECT FOR UPDATE for a few weeks now, that hasn't actually worked until just now.
* Don't include miscadmin.h in elog.h, since the former is not part ofTom Lane2000-12-06
| | | | the installed header file set.
* I've just seen what happens when the MEMORY_CONTEXT_CHECKING code firesTom Lane2000-12-05
| | | | | an error at end of transaction ... and I did *not* like it. Reduce ERROR to NOTICE so that this situation doesn't cause an infinite loop.
* In SELECT FOR UPDATE, silently ignore null CTIDs, rather than generatingTom Lane2000-12-05
| | | | | | | an error as we used to. In an OUTER JOIN scenario, retrieving a null CTID from one of the input relations is entirely expected. We still want to lock the input rows from the other relations, so just ignore the null and keep going.
* From Stephan Szabo:Tom Lane2000-12-05
| | | | | | | | | | I believe this should fix the issue that Philip Warner noticed about the check for unique constraints meeting the referenced keys of a foreign key constraint allowing the specification of a subset of a foreign key instead of rejecting it. I also added tests for a base case of this to the foreign key and alter table tests and patches for expected output.
* Repair breakage of rules containing INSERT ... SELECT actions, per bugTom Lane2000-12-05
| | | | | | | | | | | report from Joel Burton. Turns out that my simple idea of turning the SELECT into a subquery does not interact well *at all* with the way the rule rewriter works. Really what we need to make INSERT ... SELECT work cleanly is to decouple targetlists from rangetables: an INSERT ... SELECT wants to have two levels of targetlist but only one rangetable. No time for that for 7.1, however, so I've inserted some ugly hacks to make the rewriter know explicitly about the structure of INSERT ... SELECT queries. Ugh :-(
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 08:53:08 +0000