aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Teach autovacuum how to determine whether a temp table belongs to a crashedTom Lane2008-07-01
| | | | | | | backend. If so, send a LOG message to the postmaster log, and if the table is beyond the vacuum-for-wraparound horizon, forcibly drop it. Per recent discussions. Perhaps we ought to back-patch this, but it probably needs to age a bit in HEAD first.
* Issue psql connection warnings on connection start and via \c, perBruce Momjian2008-07-01
| | | | observation by David Fetter.
* Fix recovery.conf boolean variables to take the same range of stringBruce Momjian2008-06-30
| | | | values as postgresql.conf.
* Add psql TODO:Bruce Momjian2008-06-30
| | | | | | | | > o Add "auto" expanded mode that outputs in expanded format if > "wrapped" mode can't wrap the output to the screen width > > http://archives.postgresql.org/pgsql-hackers/2008-05/msg00417.php >
* Add psql TODO item:Bruce Momjian2008-06-30
| | | | | | | | | | > o Add option to wrap column values at whitespace boundaries, > rather than chopping them at a fixed width. > Currently, "wrapped" format chops values into fixed > widths. Perhaps the word wrapping could use the same > algorithm documented in the W3C specification. > http://archives.postgresql.org/pgsql-hackers/2008-05/msg00404.php > http://www.w3.org/TR/CSS21/tables.html#auto-table-layout
* ltree support for multibyte encodings. Patch was made byTeodor Sigaev2008-06-30
| | | | laser <laserlist@pgsqldb.com> with some editorization by me.
* Turn PGBE_ACTIVITY_SIZE into a GUC variable, track_activity_query_size.Heikki Linnakangas2008-06-30
| | | | | | | | | As the buffer could now be a lot larger than before, and copying it could thus be a lot more expensive than before, use strcpy instead of memcpy to copy the query string, as was already suggested in comments. Also, only copy the PgBackendStatus struct and string if the slot is in use. Patch by Thomas Lee, with some changes by me.
* Remove unnecessary coziness of GIN code with datum copying. Now thatTom Lane2008-06-29
| | | | | | space is tracked via GetMemoryChunkSpace, there's really no advantage to duplicating datumCopy's innards here. This is one bit of my toast indirection patch that should go in anyway.
* If pnstrdup is going to be promoted to a generally available function,Tom Lane2008-06-28
| | | | it ought to conform to the rest of palloc.h in using Size for sizes.
* Consider a clause to be outerjoin_delayed if it references the nullable sideTom Lane2008-06-27
| | | | | | | | | | | | | | | | | | of any lower outer join, even if it also references the non-nullable side and so could not get pushed below the outer join anyway. We need this in case the clause is an OR clause: if it doesn't get marked outerjoin_delayed, create_or_index_quals() could pull an indexable restriction for the nullable side out of it, leading to wrong results as demonstrated by today's bug report from toruvinn. (See added regression test case for an example.) In principle this has been wrong for quite a while. In practice I don't think any branch before 8.3 can really show the failure, because create_or_index_quals() will only pull out indexable conditions, and before 8.3 those were always strict. So though we might have improperly generated null-extended rows in the outer join, they'd get discarded from the result anyway. The gating factor that makes the failure visible is that 8.3 considers "col IS NULL" to be indexable. Hence I'm not going to risk back-patching further than 8.3.
* Fix standalone libpq build on win32.Magnus Hagander2008-06-27
| | | | Hiroshi Saito
* Improve planner's estimation of the size of an append relation: rather thanTom Lane2008-06-27
| | | | | | | taking the maximum of any child rel's width, we should weight the widths proportionally to the number of rows expected from each child. In hindsight this is obviously correct because row width is really a proxy for the total physical size of the relation. Per discussion with Scott Carey (bug #4264).
* Mention actual function names in documentation of how to pass binaryBruce Momjian2008-06-27
| | | | values to libpq.
* Add to TODO:Bruce Momjian2008-06-27
| | | | | | > > * Fix system views like pg_stat_all_tables to use set-returning > functions, rather than views of per-column functions
* Clarify plpgsql documentation by not treating IF THEN ELSE IF ... as aTom Lane2008-06-27
| | | | truly distinct version of IF. Per suggestion from Marko Kreen.
* Modify the recently-added probe for -Wl,--as-needed some more, because RHEL-4Tom Lane2008-06-27
| | | | | | | vintage Linux is even more broken than we realized: a link to libreadline will succeed, and fail only at runtime. It seems that an AC_TRY_RUN test is the only reliable way to check whether this is really safe. Per report from Tatsuo.
* Use SGML table to show backslash string escapes, rather than have themBruce Momjian2008-06-26
| | | | | | appear in a paragraph. Andy Anderson
* Add MERGE TODO URL:Bruce Momjian2008-06-26
| | | | > http://archives.postgresql.org/pgsql-hackers/2008-04/msg01890.php
* Fix pg_ctl bug where detection of binary location from postmaster.optsBruce Momjian2008-06-26
| | | | wasn't working.
* Fix bug "select lower('asd') = 'asd'" returns false with multibyte encodingTeodor Sigaev2008-06-26
| | | | | and non-C locale. Fix is just to use correct source's length for char2wchar call.
* Synced parserMichael Meskes2008-06-26
|
* Add TODO about security:Bruce Momjian2008-06-26
| | | | | | | * Improve server security options http://archives.postgresql.org/pgsql-hackers/2008-04/msg01875.php http://archives.postgresql.org/pgsql-hackers/2008-05/msg00000.php
* More FAQ URL updates from Curtis Gallant.Bruce Momjian2008-06-26
|
* Simplify 'pg_ctl restart' detection of first argument inBruce Momjian2008-06-26
| | | | postmaster.opts.
* Update FAQ URLs as suggested by Curtis Gallant.Bruce Momjian2008-06-26
|
* Add to TODO:Bruce Momjian2008-06-26
| | | | | | | > > * Improve LDAP authentication configuration options > > http://archives.postgresql.org/pgsql-hackers/2008-04/msg01745.php
* Fix 'pg_ctl restart' to preserve command-line arguments.Bruce Momjian2008-06-26
|
* Use SYSTEMQUOTE as concatentation to strings, rather than %s printfBruce Momjian2008-06-26
| | | | patterns, for clarity.
* Remove use of postmaster.opts.default by pg_ctl.Bruce Momjian2008-06-26
|
* Reduce the alignment requirement of type "name" from int to char, and arrangeTom Lane2008-06-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | to suppress zero-padding of "name" entries in indexes. The alignment change is unlikely to save any space, but it is really needed anyway to make the world safe for our widespread practice of passing plain old C strings to functions that are declared as taking Name. In the previous coding, the C compiler was entitled to assume that a Name pointer was word-aligned; but we were failing to guarantee that. I think the reason we'd not seen failures is that usually the only thing that gets done with such a pointer is strcmp(), which is hard to optimize in a way that exploits word-alignment. Still, some enterprising compiler guy will probably think of a way eventually, or we might change our code in a way that exposes more-obvious optimization opportunities. The padding change is accomplished in one-liner fashion by declaring the "name" index opclasses to use storage type "cstring" in pg_opclass.h. Normally btree and hash don't allow a nondefault storage type, because they don't have any provisions for converting the input datum to another type. However, because name and cstring are effectively the same thing except for padding, no conversion is needed --- we only need index_form_tuple() to treat the datum as being cstring not name, and this is sufficient. This seems to make for about a one-third reduction in the typical sizes of system catalog indexes that involve "name" columns, of which we have many. These two changes are only weakly related, but the alignment change makes me feel safer that the padding change won't introduce problems, so I'm committing them together.
* TODO item done:Bruce Momjian2008-06-24
| | | | | < o Prevent pg_dump/pg_restore from being affected by > o -Prevent pg_dump/pg_restore from being affected by
* Oops, make the MSVC build put fmgroids.h where it needs to be.Tom Lane2008-06-24
| | | | Per buildfarm results.
* Add TODO:Bruce Momjian2008-06-23
| | | | | | | > > o Allow COPY to report errors sooner > > http://archives.postgresql.org/pgsql-hackers/2008-04/msg01169.php
* Add URL for Merge.Bruce Momjian2008-06-23
|
* Backup wording improvement.Bruce Momjian2008-06-23
| | | | Joshua D. Drake
* Add to TODO:Bruce Momjian2008-06-23
| | | | > * Allow custom variables to appear in pg_settings()
* Add item:Bruce Momjian2008-06-23
| | | | | | * Implement a module capability for loading /contrib-style extensions http://archives.postgresql.org/pgsql-patches/2008-04/msg00164.php
* Add libpq comment about how to determine the format used for passingBruce Momjian2008-06-23
| | | | | | binary values. Add comments to libpq C function for parameter passing.
* Add TODO:Bruce Momjian2008-06-23
| | | | | | | | * Consider whether duplicate keys should be sorted by block/offset http://archives.postgresql.org/pgsql-hackers/2008-03/msg00558.php Create new "Sorting" TODO section.
* Merge duplicate upper/lower/initcap() routines in oracle_compat.c andBruce Momjian2008-06-23
| | | | | formatting.c to use common code; remove duplicate functions and support routines that are no longer needed.
* Fix Gen_fmgrtab.sh to not rely on hard-wired knowledge of the column numbersTom Lane2008-06-23
| | | | | | | | | | | | | | in pg_proc. Also make it not emit duplicate extern declarations, and make it a bit more bulletproof in some other small ways. Likewise fix the equally hard-wired, and utterly undocumented, knowledge in the MSVC build scripts. For testing purposes and perhaps other uses in future, pull out that portion of the MSVC scripts into a standalone perl script equivalent to Gen_fmgrtab.sh, and make it generate actually identical output, rather than just more-or-less-the-same output. Motivated by looking at Pavel's variadic function patch. Whether or not that gets accepted, we can be sure that pg_proc's column set will change again in the future; it's time to not have to deal with this gotcha.
* Seems I was too optimistic in supposing that sinval's maxMsgNum could beTom Lane2008-06-20
| | | | | | | | | | | read and written without a lock. The value itself is atomic, sure, but on processors with weak memory ordering it's possible for a reader to see the value change before it sees the associated message written into the buffer array. Fix by introducing a spinlock that's used just to read and write maxMsgNum. (We could do this with less overhead if we recognized a concept of "memory access barrier"; is it worth introducing such a thing? At the moment probably not --- I can't measure any clear slowdown from adding the spinlock, so this solution is probably fine.) Per buildfarm results.
* Rewrite the sinval messaging mechanism to reduce contention and avoidTom Lane2008-06-19
| | | | | | | | | | | | | | | | | | | | | | | | | | unnecessary cache resets. The major changes are: * When the queue overflows, we only issue a cache reset to the specific backend or backends that still haven't read the oldest message, rather than resetting everyone as in the original coding. * When we observe backend(s) falling well behind, we signal SIGUSR1 to only one backend, the one that is furthest behind and doesn't already have a signal outstanding for it. When it finishes catching up, it will in turn signal SIGUSR1 to the next-furthest-back guy, if there is one that is far enough behind to justify a signal. The PMSIGNAL_WAKEN_CHILDREN mechanism is removed. * We don't attempt to clean out dead messages after every message-receipt operation; rather, we do it on the insertion side, and only when the queue fullness passes certain thresholds. * Split SInvalLock into SInvalReadLock and SInvalWriteLock so that readers don't block writers nor vice versa (except during the infrequent queue cleanout operations). * Transfer multiple sinval messages for each acquisition of a read or write lock.
* Fix a few places that were non-multibyte-safe in tsearch configuration fileTom Lane2008-06-19
| | | | parsing. Per bug #4253 from Giorgio Valoti.
* Add URL for:Bruce Momjian2008-06-19
| | | | | o Allow pg_hba.conf to specify host names along with IP addresses > http://archives.postgresql.org/pgsql-hackers/2008-06/msg00569.php
* Improve our #include situation by moving pointer types away from theAlvaro Herrera2008-06-19
| | | | | | | corresponding struct definitions. This allows other headers to avoid including certain highly-loaded headers such as rel.h and relscan.h, instead using just relcache.h, heapam.h or genam.h, which are more lightweight and thus cause less unnecessary dependencies.
* Fix compiler warning introduced by recent patch. Tsk tsk.Tom Lane2008-06-18
|
* Improve error reporting for problems in text search configuration filesTom Lane2008-06-18
| | | | | | | | | | | by installing an error context subroutine that will provide the file name and line number for all errors detected while reading a config file. Some of the reader routines were already doing that in an ad-hoc way for errors detected directly in the reader, but it didn't help for problems detected in subroutines, such as encoding violations. Back-patch to 8.3 because 8.3 is where people will be trying to debug configuration files.
* Move wchar2char() and char2wchar() from tsearch into /mb to be easier toBruce Momjian2008-06-18
| | | | | | use for other modules; also move pnstrdup(). Clean up code slightly.
* Fix a few typos in the DTrace docs. Patch from Euler Taveira de Oliveira,Neil Conway2008-06-18
| | | | along with an additional typo I noticed along the way.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-06 09:31:55 +0000