aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
...
* Add support for Latin9 encoding in to_ascii(). Jaime CasanovaTom Lane2004-12-20
|
* Mark the TimeZone parameter as GUC_REPORT, so that JDBC can find outTom Lane2004-12-20
| | | | when it changes. Per request from Kris Jurka.
* Remove direct inclusions of <com_err.h> as well as configure test forTom Lane2004-12-20
| | | | | | | its presence. This amounts to desupporting Kerberos 5 releases 1.0.*, which is small loss, and simplifies use of our Kerberos code on platforms with Red-Hat-style include file layouts. Per gripe from John Gray and followup discussion.
* Allow NetBSD, m64k to compile the ASM spinlock code.Bruce Momjian2004-12-18
| | | | R?mi Zara
* Make array_cat more paranoid about checking datatypes in empty arrays.Tom Lane2004-12-17
|
* array_map failed to insert correct result type in an empty array.Tom Lane2004-12-17
| | | | Per example from Florian Pflug.
* Fix is-it-time-for-a-checkpoint logic so that checkpoint_segments canTom Lane2004-12-17
| | | | usefully be larger than 255. Per gripe from Simon Riggs.
* Translation updatesPeter Eisentraut2004-12-16
|
* Fix another place broken by new List implementation :-(. Per exampleTom Lane2004-12-15
| | | | | from goranpop@nspoint.net. I think this escaped notice because in simple cases the list is NIL on entry.
* Disallow SETOF in the input of parseTypeString(). Formerly it wasTom Lane2004-12-15
| | | | | | | silently ignored, allowing one to write bizarre things like DECLARE x setof int; in plpgsql. This has misled at least one novice into thinking that plpgsql variables could be sets ...
* Calculation of keys_are_unique flag was wrong for cases involvingTom Lane2004-12-15
| | | | redundant cross-datatype comparisons. Per example from Merlin Moncure.
* Translation updatePeter Eisentraut2004-12-15
|
* New translationPeter Eisentraut2004-12-13
|
* Translation updatesPeter Eisentraut2004-12-13
|
* Translation updatesPeter Eisentraut2004-12-13
|
* Avoid generating excess (and illegal) parentheses around an aliased JOINTom Lane2004-12-13
| | | | in prettyprint mode. Andreas Pflug
* PREPARE and EXPLAIN need to copy the source query just like we recentlyTom Lane2004-12-12
| | | | | | had to do in DECLARE CURSOR. AFAICS these are all the places affected. PREPARE case per example from Michael Fuhr, EXPLAIN case located by grepping for planner calls ...
* Translation updatesPeter Eisentraut2004-12-12
|
* Upgrade formrdesc() so that it can correctly initialize the tupledescTom Lane2004-12-12
| | | | | | | | | | | (rd_att) field of a nailed-in-cache relcache entry. This fixes the bug reported by Alvaro 8-Dec-2004; I believe it probably also explains Grant Finnemore's report of 10-Sep-2004. In an unrelated change in the same file, put back 7.4's response to failure to rename() the relcache init file, ie, unlink the useless temp file. I did not put back the warning message, since there might actually be some reason not to have that.
* Instead of supposing (wrongly, in the general case) that the rowtypeTom Lane2004-12-11
| | | | | | | | of an inheritance child table is binary-compatible with the rowtype of its parent, invent an expression node type that does the conversion correctly. Fixes the new bug exhibited by Kris Shannon as well as a lot of old bugs that would only show up when using multiple inheritance or after altering the parent table.
* Translation updatesPeter Eisentraut2004-12-11
|
* Translation updatesPeter Eisentraut2004-12-11
|
* Translation updatesPeter Eisentraut2004-12-11
|
* Translation updatesPeter Eisentraut2004-12-11
|
* Translation updatesPeter Eisentraut2004-12-11
|
* Translation updatesPeter Eisentraut2004-12-11
|
* ActiveSnapshot must be set to something valid while running deferredTom Lane2004-12-06
| | | | triggers during COMMIT. Per trouble report from Frank van Vugt.
* Back out addition of Win1252 encoding.Bruce Momjian2004-12-04
|
* Use StrNCpy not strncpy to fill hash key, to ensure the resulting keyTom Lane2004-12-03
| | | | | | is null-terminated. I think this is not a real bug because the parser would always have truncated the identifier to NAMEDATALEN-1 already, but let's be safe. Per report from Klocwork.
* > If it bothers you that much. I'd make a flag, cleared at the start ofBruce Momjian2004-12-03
| | | | | | | > each COPY, and then where we test for CR or LF in CopyAttributeOutCSV, > if the flag is not set then set it and issue the warning. Andrew Dunstan
* Back out fix for Unicode characters above 0x10000Bruce Momjian2004-12-03
|
* > I have installed your patch and adjusted the names of the standardsBruce Momjian2004-12-02
| | | | | | | | | | | | | | | | | | | > throughout to the spellings suggested by your book. Great. A follow-up patch for current CVS HEAD is attached, and available at http://troels.arvin.dk/db/pgsql/conformance/pgsql-sql-conformance- followup.patch The patch - includes a core feature ID that had been left out by mistake (C011) - updates the sql_feature_packages.txt table to reflect changes in SQL:2003 which were not covered properly in my last patch Troels Arvin
* > I enclose a short patch to reduce the PGARCH_RESTART_INTERVAL from 60Bruce Momjian2004-12-02
| | | | | | | | | | | | | | | | | | | | > seconds to 10 seconds. The original number was plucked from thin air > some months ago, and I'd like to review that now based upon further > thought, observation and experience. > > This change has little or no effect on performance, since the interval > is there mainly to avoid repeated respawn attempts if archiver fails at > startup. Archiver start-up time is very quick, so there is little danger > of exceeding 10 seconds. > > On a busy system, if the archiver does die, then many files can build up > in the 60 seconds before respawning. That xlog file backlog could take > some time to clear. This then leaves a larger than normal window of data > loss for a possibly long period. > > It's a minor change only, with no other effect on function. Simon Riggs
* Fix for Unicode characters above 0x10000.Bruce Momjian2004-12-02
| | | | John Hansen
* On win32, there is currently no way to get the equivalent function ofBruce Momjian2004-12-02
| | | | | | | | | | | | | | | the "ps" argument list on Unix - meaning that there is no way to identify for example the stats processors or the bgwriter. This patch adds this functionality, in a bit of a crufty way. It creates a kernel Event object with the name of what would be in the title. This can be viewed using for example Process Explorer. It's been very handy for me during both debugging and using. I haven't figured a better way, but perhaps someone has one that's less crufty? If not, here is at least a working patch :-) Magnus Hagander
* Add Charset WIN1252 support.Bruce Momjian2004-12-02
| | | | Roland Volkmann
* Change Win32 dlerror message to:Bruce Momjian2004-12-02
| | | | return "dynamic loading error";
* Disallow the combination VACUUM FULL FREEZE for safety's sake, for theTom Lane2004-12-02
| | | | | | | | | reasons I outlined in pghackers a few days ago. Also, undo someone's overly optimistic decision to reduce tuple state checks from if (...) elog() to Asserts. If I trusted this code more, I might think it was a good idea to disable these checks in production installations. But I don't.
* Teach regex_fixed_prefix() the correct handling of advanced regexTom Lane2004-12-02
| | | | | | escapes --- they aren't simply quoted characters. Problem noted by Antti Salmela. Also fix problem with incorrect handling of multibyte characters when followed by a quantifier.
* Make some adjustments to reduce platform dependencies in plan selection.Tom Lane2004-12-02
| | | | | | | | | | In particular, there was a mathematical tie between the two possible nestloop-with-materialized-inner-scan plans for a join (ie, we computed the same cost with either input on the inside), resulting in a roundoff error driven choice, if the relations were both small enough to fit in sort_mem. Add a small cost factor to ensure we prefer materializing the smaller input. This changes several regression test plans, but with any luck we will now have more stability across platforms.
* Fix timestamptz_age() to do calculation in local timezone not GMT, per bug 1332.Tom Lane2004-12-01
|
* Change planner to use the current true disk file size as its estimate ofTom Lane2004-12-01
| | | | | | | | | | | | | | | | | a relation's number of blocks, rather than the possibly-obsolete value in pg_class.relpages. Scale the value in pg_class.reltuples correspondingly to arrive at a hopefully more accurate number of rows. When pg_class contains 0/0, estimate a tuple width from the column datatypes and divide that into current file size to estimate number of rows. This improved methodology allows us to jettison the ancient hacks that put bogus default values into pg_class when a table is first created. Also, per a suggestion from Simon, make VACUUM (but not VACUUM FULL or ANALYZE) adjust the value it puts into pg_class.reltuples to try to represent the mean tuple density instead of the minimal density that actually prevails just after VACUUM. These changes alter the plans selected for certain regression tests, so update the expected files accordingly. (I removed join_1.out because it's not clear if it still applies; we can add back any variant versions as they are shown to be needed.)
* Avoid scribbling on original parsetree during DECLARE CURSOR. ThisTom Lane2004-11-28
| | | | | | prevents problems when the DECLARE is in a portal and is executed repeatedly, as is possible in v3 protocol. Per analysis by Oliver Jowett, though I didn't use his patch exactly.
* Work around lack of NLS support in libpgport by making those componentsPeter Eisentraut2004-11-27
| | | | | | who use it scan the relevant source files for their own catalog. It creates a bit of duplicate work for translators, but it gets the job done for now.
* Update of conformance information to SQL:2003Peter Eisentraut2004-11-27
| | | | | | by Troels Arvin, Simon Riggs, Elein Mustain Make spelling of SQL standard names uniform.
* Install Tcl regex fixes to sync our regex engine with Tcl 8.4.8 (up fromTom Lane2004-11-24
| | | | | 8.4.1). This corrects some curious regex bugs, though not the greediness issue I was hoping to find a solution for :-(
* Our interface code for Spencer's regexp package was checking for regexpTom Lane2004-11-24
| | | | | | | error conditions during regexp compile, but not during regexp execution; any sort of "can't happen" errors would be treated as no-match instead of being reported as they should be. Noticed while trying to duplicate a reported Tcl bug.
* A client_encoding specification coming from the connection request hasTom Lane2004-11-24
| | | | | | | | | | to be processed by GUC before InitPostgres, because any required lookup of the encoding conversion function has to be done during InitializeClientEncoding. So, I broke this last week by moving GUC processing to after InitPostgres :-(. What we can do as a compromise is process non-SUSET variables during command line scanning (the same as before), and postpone the processing of only SUSET variables. None of the SUSET variables need to be set before InitPostgres.
* Assert that BufferIsPinned() in IncrBufferRefCount(), rather than usingNeil Conway2004-11-24
| | | | | a home-brewed combination of assertions that boiled down to the same thing.
* Fix rounding problem in dynahash.c's decision about when the targetTom Lane2004-11-21
| | | | | | | | fill factor has been exceeded. We usually run with ffactor == 1, but the way the test was coded, it wouldn't split a bucket until the actual fill factor reached 2.0, because of use of integer division. Change from > to >= so that it will split more aggressively when the table starts to get full.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 03:21:34 +0000