aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
* Add extern int optreset declaration, per bug report from <info@decc.nl>.Peter Eisentraut2001-04-19
|
* Fix "off by VARHDRSZ" bug in (Cyrillic) recode support.Peter Eisentraut2001-04-19
|
* Kluge solution for Alex Pilosov's report of problems with whole-tupleTom Lane2001-04-19
| | | | | | | | | function arguments in join queries: copy the tuples into TransactionCommandContext so they don't get recycled too soon. This is horrid, but not any worse than 7.0 or before, which also leaked such tuples until end of query. A proper fix will require allowing tuple datums to be physically stored inside larger tuple datums, which opens up a bunch of issues that can't realistically be solved for 7.1.1.
* Add a crash gurard to pg_encoding_mblen in case of an invalid encodingTatsuo Ishii2001-04-19
| | | | given.
* Further tweaking of error messages for cases involving attributes &Tom Lane2001-04-18
| | | | | | functions of join or subselect aliases. It'd be awfully nice if this code knew for sure whether it was dealing with 'x.f' or 'f(x)' syntax; maybe we can fix that in a future cycle.
* Make the world safe for passing whole rows of views to functions. ThisTom Lane2001-04-18
| | | | already worked fine for whole rows of tables, but not so well for views...
* Make rule lister do the right thing with Vars representing whole tuples.Tom Lane2001-04-18
|
* Add some defenses to guard against case where a rule refers to a tableTom Lane2001-04-17
| | | | | | | or view that's been dropped and then recreated with the same name (but, perhaps, different columns). Eventually we'd like to support this but for now all we can do is fail cleanly, rather than possibly coredumping if we proceed using the obsolete rule.
* Avoid reversing user-given order of WHERE clauses while attaching clausesTom Lane2001-04-16
| | | | | | | | to specific base or join RelOptInfo nodes during planning. This preserves the more-intuitive behavior of 7.0.* --- if you write an expensive clause (such as a sub-select) last, it should get evaluated last. Someday we ought to try to have some intelligence about the order of evaluation of WHERE clauses, but for now we should not override what the user wrote.
* Correction for mathematical properties in Unicode converison maps.Tatsuo Ishii2001-04-16
| | | | Patches contributed by Eiji Tokuya (e-tokuya@sankyo-unyu.co.jp)
* getdatabaseencoding() and PG_encoding_to_char() were being sloppy aboutTom Lane2001-04-16
| | | | | converting char* strings to type 'name'. Imagine my surprise when 7.1 release coredumped upon start when compiled --enable-multibyte ...
* Remove error report from pq_endmessage when pq_putmessage fails. TheTom Lane2001-04-16
| | | | | | | | only possible failure is in pq_flush, which will log a (better!) report anyway --- so pq_endmessage is just cluttering the log with a redundant entry. This matters when a client crashes partway through a large query, since we will emit many broken-pipe reports before finishing the query and exiting.
* Constant expressions that appear in ORDER BY, GROUP BY, DISTINCT ONTom Lane2001-04-15
| | | | | | | | lists should be reverse-compiled into targetlist index numbers, because that's the only interpretation the parser allows for a constant in these clauses. (Ergo, the only way they could have gotten into the list in the first place is to have come from the targetlist; so this should always work.) Per problem report from Peter E.
* Prevent generation of invalid plans for RIGHT or FULL joins with multipleTom Lane2001-04-15
| | | | | | | | join clauses. The mergejoin executor wants all the join clauses to appear as merge quals, not as extra joinquals, for these kinds of joins. But the planner would consider plans in which partially-sorted input paths were used, leading to only some of the join clauses becoming merge quals. This is fine for inner/left joins, not fine for right/full joins.
* Add debug_query_string global variable for pgmonitor and debugging use.Bruce Momjian2001-04-14
|
* Another try at making numeric MODULO operator produce the right answer.Tom Lane2001-04-14
| | | | | | Although it was now using the right equation, it was making bogus choices of the precision to compute intermediate results to. I'm not sure this is really right even yet, but it's better than before ...
* Fix comment that Vadim found confusing.Tom Lane2001-04-05
|
* StartupXLOG(): initialize XLogCtl->Insert to new page if there isVadim B. Mikheev2001-04-05
| | | | no room for a record on last log page.
* Fix/cleanup DLLLIBS handling for Cygwin port. If it works it's toTom Lane2001-04-04
| | | | Jason Tishler's credit, if it's broken it's my fault ...
* Have to lock buffer while changing page' LSN.Vadim B. Mikheev2001-04-04
| | | | Thanks to Tom.
* Log sequence creation (to initialize magic number on recovery).Vadim B. Mikheev2001-04-03
|
* Correct bogus mktime() calls.Tom Lane2001-04-03
|
* Check for failure of malloc() and realloc() when allocating space forTom Lane2001-04-03
| | | | | | VFD entries. On platforms where dereferencing a null pointer doesn't lead to coredump, it's possible that this omission could have led to unpleasant behavior like deleting the wrong file.
* open(2) flags saved for re-opening a virtual file should probably notTom Lane2001-04-03
| | | | include O_CREAT.
* Restore pre-7.1 behavior of allowing DROP of a table whose underlyingTom Lane2001-04-02
| | | | | | physical file has disappeared. There is no really good reason why relcache should be opening the underlying file at all, AFAICS. In any case we needn't raise a hard error here.
* _mdfd_getrelnfd() should include kernel error code in failure message.Tom Lane2001-04-02
|
* Complain if the same column name is inherited from multiple parentsTom Lane2001-04-02
| | | | | | with different default values, unless the child table redeclares the column with an explicit default. This was judged to be the approach least likely to cause unpleasant surprises.
* Disable creation of indexes on system tables.Bruce Momjian2001-04-02
|
* Remove duplicate definition of DLLLIBS, per gripe from Fred Yankowski.Tom Lane2001-04-02
|
* Tom Ivar Helbekkmo <tih@kpnQwest.no> says that dynamic linking worksTom Lane2001-04-02
| | | | now on VAX NetBSD. Hence, remove #ifdef'd disable tests.
* Planner wasn't correctly handling adjustment of tuple_fraction for theTom Lane2001-04-01
| | | | case of LIMIT in a sub-select.
* Re-allow specification of a new default value for an inherited columnTom Lane2001-03-30
| | | | | | in CREATE TABLE, but give a warning notice. Clean up inconsistent handling of defaults and NOT NULL flags from multiply-inherited columns. Per pghackers discussion 28-Mar through 30-Mar.
* Rename 'random_seed' back to 'seed'.Peter Eisentraut2001-03-29
|
* Quick hack to fix Oliver Elphick's problem with subselects in anTom Lane2001-03-27
| | | | | | | inheritance query: make duplicate copies of subplans in adjust_inherited_attrs. When we redesign querytrees we really gotta do something about this issue of whether querytrees are read-only and can share substructure or not.
* Repair pgindent damage to comments.Tom Lane2001-03-27
|
* The following patch updates the FAQ_AIX and makes C++ code work withBruce Momjian2001-03-27
| | | | | | | | | | | | | | | | | | more recent versions of the IBM C++ compiler (now called VisualAge C++). The C++ part was previously broken (g++ and xlC), thus this is zero risk. Only AIX specific parts are touched (1 Makefile.shlib line (link with $(COMPILER ) instead of $(CC) and one shell script line (parameter -C to nm to not demangle C++ symbo ls for .exp file)). I thus ask you to please apply this patch before release. With or without this patch RC1 on AIX 4.3.2 RS6000 passes "gmake check" for both the native compiler vac.C 5.0.1 and gcc 2.95.2 :-) Andreas
* Spell __volatile__ correctly.Tom Lane2001-03-27
|
* Add period to message.Bruce Momjian2001-03-26
|
* Change message to _the_ administrator. There is only one administrativeBruce Momjian2001-03-26
| | | | | | account. This connection has been terminated by the administrator.
* Fix unportable assumptions about alignment of local char[n] variables.Tom Lane2001-03-25
|
* Fix code that incorrectly assumed a 'char foo[N]' local variable wouldTom Lane2001-03-25
| | | | be aligned on a word boundary. Per report from Steve Nicolai.
* When using 'long long int' for int64 type, check to see if the compilerTom Lane2001-03-23
| | | | | | accepts nnnLL syntax for long long constants. If so, decorate the CRC64 constants with LL to avoid warnings and/or erroneous results from certain non-standards-compliant compilers.
* Mark exception and assert global variables as DLLIMPORT, so that plpgsqlTom Lane2001-03-23
| | | | can be compiled with asserts enabled on Windoze.
* Fix comments that were mis-wrapped, for Tom Lane.Bruce Momjian2001-03-23
|
* Fix Joubert's complaint that int8-sized numeric literals are mishandledTom Lane2001-03-22
| | | | | | | | | on Alpha (because parser mistakenly assumes that a nonoverflow result from strtol means the value will fit into int4). A scan for other uses of strtol and strtoul found a couple other places with the same mistake; fix them too. The changes are all conditional on HAVE_LONG_INT_64 to avoid complaints from compilers that think x != x is a silly test (cf. pg_atoi).
* Remove dashes in comments that don't need them, rewrap with pgindent.Bruce Momjian2001-03-22
|
* pgindent run. Make it all clean.Bruce Momjian2001-03-22
|
* Check bufHdr->cntxDirty and call StartBufferIO in BufferSync()Vadim B. Mikheev2001-03-21
| | | | | | | | *before* acquiring shlock on buffer context. This way we should be protected against conflicts with FlushRelationBuffers. (Seems we never do excl lock and then StartBufferIO for the same buffer, so there should be no deadlock here, - but we'd better check this very soon).
* Fix 'ps' WAIT status display bug on setproctitle() platforms, cleared byBruce Momjian2001-03-20
| | | | Tom Lane.
* Tweak out-of-memory error messages to include the request size, so thatTom Lane2001-03-19
| | | | | it's easier to tell whether a bug report is talking about progressive memory exhaustion or a wacko requested chunk size.