- 27 4月, 2006 13 次提交
-
-
由 Tom Lane 提交于
then we should export a reasonable set of the supporting routines too.
-
由 Bruce Momjian 提交于
In the SSL code in libpq it does some processing with DH parameters: SSL_CTX_set_tmp_dh_callback() This function is marked as server use only[1], the client always uses the DH parameters in the server, so all the code in the client dealing with the DH parameters is useless. This patch removes it. It's not clear why the code was added in the first place, it's been there almost since the beginning[2]. At the time there was a suggestion of merging the front-end and backend SSL code, but looking at the changes since, that seems unlikely. As a further example, the s_server program allows you to specify DH params, but s_client doesn't. In the GnuTLS documentation under gnutls_dh_params_generate2() it says[3]: Also note that the DH parameters are only useful to servers. Since clients use the parameters sent by the server, it's of no use to call this in client side.
-
由 Bruce Momjian 提交于
CONSTRAINT, rather than affecting all constraints in all schemas (which is what we used to do). Also allow schema specifications. Kris Jurka
-
由 Bruce Momjian 提交于
shutdown, or when requested by a backend: It changes so the file is only written once every 5 minutes (changeable of course, I just picked something) instead of once every half second. It's still written when the stats collector shuts down, just as before. And it is now also written on backend request. A backend requests a rewrite by simply sending a special stats message. It operates on the assumption that the backends aren't actually going to read the statistics file very often, compared to how frequent it's written today. Magnus Hagander
-
由 Bruce Momjian 提交于
Philip Yarra
-
由 Bruce Momjian 提交于
improve examples. Mark Kirkwood
-
由 Bruce Momjian 提交于
pg_freespacemap_relations and pg_freespacemap_pages. Mark Kirkwood
-
由 Bruce Momjian 提交于
tracks index pages, not free space on pages): 1/ Index free bytes set to NULL 2/ Comment added to the README briefly mentioning the index business 3/ Columns reordered more logically 4/ 'Blockid' column removed 5/ Free bytes column renamed to just 'bytes' instead of 'blockfreebytes' Mark Kirkwood
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
pg_resetxlog. Simon
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Matteo Beccati
-
- 26 4月, 2006 7 次提交
-
-
由 Bruce Momjian 提交于
information, and add a -r option to reset pg_control without affecting xlog. yuanjia lee
-
由 Bruce Momjian 提交于
* -Allow WAL information to recover corrupted pg_controldata
-
由 Tom Lane 提交于
set to the large object context ("fscxt"), as this is inevitably a source of transaction-duration memory leaks. Not sure why we'd not noticed it before; maybe people weren't touching a whole lot of LOs in the same transaction before the 8.1 pg_dump changes. Per report from Wayne Conrad. Backpatched as far as 8.1, but the problem doubtless goes all the way back. I'm disinclined to spend the time to try to verify that the older branches would still work if patched, seeing that this code was significantly modified for 8.0 and again for 8.1, and that we don't have any trouble reports before 8.1. (Maybe the leaks were smaller before?)
-
由 Tom Lane 提交于
thereby saving a visit to the metapage in most index searches/updates. This wouldn't actually save any I/O (since in the old regime the metapage generally stayed in cache anyway), but it does provide a useful decrease in bufmgr traffic in high-contention scenarios. Per my recent proposal.
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
implied by the predicate of a partial index being used to scan a table. However, this optimization is unsafe in an UPDATE, DELETE, or SELECT FOR UPDATE query, because the quals need to be rechecked by EvalPlanQual if there's an update conflict. Per example from Jean-Samuel Reynaud.
-
- 25 4月, 2006 20 次提交
-
-
由 Bruce Momjian 提交于
configure.
-
由 Bruce Momjian 提交于
equals sign.
-
由 Bruce Momjian 提交于
David Wheeler
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
documentation sections. Also update SET/RESET to be consistent. Nicolas Barbier
-
由 Bruce Momjian 提交于
use RESET CONNECTION: < * Add RESET SESSION command to reset all session state > * Add RESET CONNECTION command to reset all session state 447c447 < notify the protocol when a RESET SESSION command is used. > notify the protocol when a RESET CONNECTION command is used.
-
由 Bruce Momjian 提交于
< * Add RESET CONNECTION command to reset all session state > * Add RESET SESSION command to reset all session state 447c447 < notify the protocol when a RESET CONNECTION command is used. > notify the protocol when a RESET SESSION command is used.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Hans-J?rgen Sch?nig
-
由 Bruce Momjian 提交于
< o %Prevent child tables from altering or dropping constraints < like CHECK that were inherited from the parent table < like CHECK that are inherited by child tables < < Dropping constraints should only be possible with CASCADE. < > like CHECK that are inherited by child tables unless CASCADE > is used > o %Prevent child tables from altering or dropping constraints > like CHECK that were inherited from the parent table
-
由 Tatsuo Ishii 提交于
(pgsql-committers@postgresql.org).
-
由 Bruce Momjian 提交于
> * -Add transaction_timestamp(), statement_timestamp(), clock_timestamp()
-
由 Bruce Momjian 提交于
transaction_timestamp() (just like now()). Also update statement_timeout() to mention it is statement arrival time that is measured. Catalog version updated.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
o Support ISO INTERVAL syntax if units cannot be determined from the string, and are supplied after the string The SQL standard states that the units after the string specify the units of the string, e.g. INTERVAL '2' MINUTE should return '00:02:00'. The current behavior has the units restrict the interval value to the specified unit or unit range, INTERVAL '70' SECOND returns '00:00:10'. For syntax that isn't uniquely ISO or PG syntax, like '1' or '1:30', treat as ISO if there is a range specification clause, and as PG if there no clause is present, e.g. interpret '1:30' MINUTE TO SECOND as '1 minute 30 seconds', and interpret '1:30' as '1 hour, 30 minutes'. This makes common cases like SELECT INTERVAL '1' MONTH SQL-standard results. The SQL standard supports a limited number of unit combinations and doesn't support unit names in the string. The PostgreSQL syntax is more flexible in the range of units supported, e.g. PostgreSQL supports '1 year 1 hour', while the SQL standard does not.
-
由 Bruce Momjian 提交于
o -Add support for day-time syntax, INTERVAL '1 2:03:04'DAY TO SECOND
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO SECOND
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-