</DL><p>

                        <DT><a name="PostgreSQL" href="#PostgreSQL"><H3 ADD_DATE="1333386475">PostgreSQL</H3></a>

                        <DL><p>

                            <DT><a name="disk space" href="#disk space"><H3 ADD_DATE="1340661986">disk space</H3></a>

                            <DL><p>

                                <DT><a name="quotas" href="#quotas"><H3 ADD_DATE="1373521860">quotas</H3></a>

                                </DL><p>

                                <DT><A HREF="http://dba.stackexchange.com/questions/3491/postgresql-disk-space-not-released-after-truncate" name="http://dba.stackexchange.com/questions/3491/postgresql-disk-space-not-released-after-truncate" ADD_DATE="1340661221" ICON_URI="http://cdn.sstatic.net/dba/img/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://cdn.sstatic.net/dba/img/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Disk space not released after TRUNCATE - Database Administrators</A><a name="PostgreSQL: Disk space not released after TRUNCATE - Database Administrators" href="#PostgreSQL: Disk space not released after TRUNCATE - Database Administrators" style="margin-left: 0.5em;">&para;</a>

                                <DT><A HREF="https://issues.apache.org/jira/browse/JENA-28" name="https://issues.apache.org/jira/browse/JENA-28" ADD_DATE="1340661975" ICON_URI="https://issues.apache.org/jira/s/en_UKd9dgiy/731/4/_/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="https://issues.apache.org/jira/s/en_UKd9dgiy/731/4/_/favicon.ico" style="margin-right: 0.5em;"/>[#JENA-28] Drop Temporary Tables in Postgres (PATCH) - ASF JIRA</A><a name="[#JENA-28] Drop Temporary Tables in Postgres (PATCH) - ASF JIRA" href="#[#JENA-28] Drop Temporary Tables in Postgres (PATCH) - ASF JIRA" style="margin-left: 0.5em;">&para;</a>

                                <DT><A HREF="http://www.postgresql.org/docs/8.3/static/sql-cluster.html" name="http://www.postgresql.org/docs/8.3/static/sql-cluster.html" ADD_DATE="1340665221" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 8.3: CLUSTER</A><a name="PostgreSQL: Documentation: 8.3: CLUSTER" href="#PostgreSQL: Documentation: 8.3: CLUSTER" style="margin-left: 0.5em;">&para;</a>

                                <DT><A HREF="http://archives.postgresql.org/pgsql-sql/2006-09/msg00142.php" name="http://archives.postgresql.org/pgsql-sql/2006-09/msg00142.php" ADD_DATE="1340668156" LAST_CHARSET="UTF-8"><img width="16" height="16" src="blank.gif" style="margin-right: 0.5em;"/>Re: ERROR: could not write block 196261 of temporary file: No space left</A><a name="Re: ERROR: could not write block 196261 of temporary file: No space left" href="#Re: ERROR: could not write block 196261 of temporary file: No space left" style="margin-left: 0.5em;">&para;</a>

                                <DT><A HREF="http://postgresql-in.blogspot.com/2008/04/postgresql-in-place-update.html" name="http://postgresql-in.blogspot.com/2008/04/postgresql-in-place-update.html" ADD_DATE="1340673360" ICON_URI="http://postgresql-in.blogspot.com/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://postgresql-in.blogspot.com/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: PostgreSQL: In place UPDATE</A><a name="PostgreSQL: PostgreSQL: In place UPDATE" href="#PostgreSQL: PostgreSQL: In place UPDATE" style="margin-left: 0.5em;">&para;</a>

if you try to disable a foreign key constraint's trigger, you will get an error, even if it is marked NOT VALID: 

"ERROR: permission denied: "RI_ConstraintTrigger_..." is a system trigger

SQL state: 42501"

                                <DT><A HREF="http://www.postgresql.org/docs/9.1/static/sql-analyze.html" name="http://www.postgresql.org/docs/9.1/static/sql-analyze.html" ADD_DATE="1377904843" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.1: ANALYZE</A><a name="PostgreSQL: Documentation: 9.1: ANALYZE" href="#PostgreSQL: Documentation: 9.1: ANALYZE" style="margin-left: 0.5em;">&para;</a>

<DD>&quot;the autovacuum daemon (see Section 23.1.5) takes care of automatic analyzing of tables when they are first loaded with data, and as they change throughout regular operation&quot;

                                <DT><A HREF="http://www.postgresql.org/docs/9.1/static/plpgsql-statements.html#PLPGSQL-STATEMENTS-SQL-ONEROW" name="http://www.postgresql.org/docs/9.1/static/plpgsql-statements.html#PLPGSQL-STATEMENTS-SQL-ONEROW" ADD_DATE="1379915256" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.1: Basic Statements: 39.5.4. Executing Dynamic Commands</A><a name="PostgreSQL: Documentation: 9.1: Basic Statements: 39.5.4. Executing Dynamic Commands" href="#PostgreSQL: Documentation: 9.1: Basic Statements: 39.5.4. Executing Dynamic Commands" style="margin-left: 0.5em;">&para;</a>

<DD>&quot;For some types of errors, the server reports the name of a database object (a table, table column, data type, or constraint) associated with the error; for example, the name of the unique constraint that caused a unique_violation error. Such names are supplied in separate fields of the error report message so that applications need not try to extract them from the possibly-localized human-readable text of the message. As of PostgreSQL 9.3, complete coverage for this feature exists only for errors in SQLSTATE class 23 (integrity constraint violation), but this is likely to be expanded in future.&quot;

this is especially useful for error parsing in column-based import [wiki.vegpath.org/Column-based_import] (and may even have been motivated by it!)

                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/app-psql.html#APP-PSQL-PATTERNS" name="http://www.postgresql.org/docs/9.3/static/app-psql.html#APP-PSQL-PATTERNS" ADD_DATE="1392338475" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: psql</A><a name="PostgreSQL: Documentation: 9.3: psql" href="#PostgreSQL: Documentation: 9.3: psql" style="margin-left: 0.5em;">&para;</a>

                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-VACUUM-COST" name="http://www.postgresql.org/docs/9.3/static/runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-VACUUM-COST" ADD_DATE="1394165454" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: Resource Consumption: 18.4.4. Cost-based Vacuum Delay</A><a name="PostgreSQL: Documentation: 9.3: Resource Consumption: 18.4.4. Cost-based Vacuum Delay" href="#PostgreSQL: Documentation: 9.3: Resource Consumption: 18.4.4. Cost-based Vacuum Delay" style="margin-left: 0.5em;">&para;</a>

<DD>&quot;During the execution of VACUUM and ANALYZE commands, the system maintains an internal counter that keeps track of the estimated cost of the various I/O operations that are performed. When the accumulated cost reaches a limit (specified by vacuum_cost_limit), the process performing the operation will sleep for a short period of time, as specified by vacuum_cost_delay. Then it will reset the counter and continue execution.&quot;

"This feature is disabled by default for manually issued VACUUM commands." however, *autovacuum*_vacuum_cost_delay is *enabled* by default

                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/ddl-schemas.html" name="http://www.postgresql.org/docs/9.3/static/ddl-schemas.html" ADD_DATE="1393374155" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: Schemas</A><a name="PostgreSQL: Documentation: 9.3: Schemas" href="#PostgreSQL: Documentation: 9.3: Schemas" style="margin-left: 0.5em;">&para;</a>

<DD>&quot;pg_catalog is always effectively part of the search path. If it is not named explicitly in the path then it is implicitly searched before searching the path&#39;s schemas. This ensures that built-in names will always be findable. However, you can explicitly place pg_catalog at the end of your search path if you prefer to have user-defined names override built-in names.&quot;

                                <DT><A HREF="http://www.postgresql.org/docs/8.4/static/logfile-maintenance.html" name="http://www.postgresql.org/docs/8.4/static/logfile-maintenance.html" ADD_DATE="1333386461" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: Manuals: Log File Maintenance</A><a name="PostgreSQL: Documentation: Manuals: Log File Maintenance" href="#PostgreSQL: Documentation: Manuals: Log File Maintenance" style="margin-left: 0.5em;">&para;</a>

                                <DT><A HREF="http://www.postgresql.org/docs/9.1/interactive/index.html" name="http://www.postgresql.org/docs/9.1/interactive/index.html" ADD_DATE="1317673868" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: Manuals: PostgreSQL 9.1: PostgreSQL 9.1.1 Documentation</A><a name="PostgreSQL: Documentation: Manuals: PostgreSQL 9.1: PostgreSQL 9.1.1 Documentation" href="#PostgreSQL: Documentation: Manuals: PostgreSQL 9.1: PostgreSQL 9.1.1 Documentation" style="margin-left: 0.5em;">&para;</a>

                                <DT><A HREF="http://www.postgresql.org/docs/8.3/static/app-psql.html" name="http://www.postgresql.org/docs/8.3/static/app-psql.html" ADD_DATE="1325722373" ICON_URI="http://www.postgresql.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: Manuals: psql</A><a name="PostgreSQL: Documentation: Manuals: psql" href="#PostgreSQL: Documentation: Manuals: psql" style="margin-left: 0.5em;">&para;</a>

                            </DL><p>

                            <DT><a name="vacuuming" href="#vacuuming"><H3 ADD_DATE="1377911873">vacuuming</H3></a>

                            <DL><p>

                                <DT><A HREF="http://postgresql.1045698.n5.nabble.com/How-can-I-tell-if-I-m-autovacuuming-td2085097.html" name="http://postgresql.1045698.n5.nabble.com/How-can-I-tell-if-I-m-autovacuuming-td2085097.html" ADD_DATE="1394169885" ICON_URI="http://postgresql.1045698.n5.nabble.com/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://postgresql.1045698.n5.nabble.com/favicon.ico" style="margin-right: 0.5em;"/>** PostgreSQL - admin - How can I tell if I&#39;m autovacuuming?</A><a name="** PostgreSQL - admin - How can I tell if I&#39;m autovacuuming?" href="#** PostgreSQL - admin - How can I tell if I&#39;m autovacuuming?" style="margin-left: 0.5em;">&para;</a>

<DD>page's own description: How can I tell if I&#39;m autovacuuming?. From what I see in the docs, these three settings in postgresql.conf should be enough for PostgreSQL (8.2) to autovacuum with the default settings: autovacuum...

in your server log, by setting log_min_messages to 'debug1' in your

postgresql.conf."

                                <DT><A HREF="http://postgresql.1045698.n5.nabble.com/Lock-problem-with-autovacuum-truncating-heap-td4265539.html" name="http://postgresql.1045698.n5.nabble.com/Lock-problem-with-autovacuum-truncating-heap-td4265539.html" ADD_DATE="1377912054" ICON_URI="http://postgresql.1045698.n5.nabble.com/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://postgresql.1045698.n5.nabble.com/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL - hackers - Lock problem with autovacuum truncating heap</A><a name="PostgreSQL - hackers - Lock problem with autovacuum truncating heap" href="#PostgreSQL - hackers - Lock problem with autovacuum truncating heap" style="margin-left: 0.5em;">&para;</a>

<DD>page's own description: Lock problem with autovacuum truncating heap. We have run across a problem with autovacuum that occurs when it can truncate off a large amount of empty blocks. It behaves different in version 9.0...

<DD>page's own description: Free HTML XHTML CSS JavaScript jQuery XML DOM XSL XSLT RSS AJAX ASP .NET PHP SQL tutorials, references, examples for web building.

        </DL><p>

        <DT><A HREF="https://www.google.com/search?q=%s" name="https://www.google.com/search?q=%s" ADD_DATE="1318464507" ICON_URI="https://www.google.com/favicon.ico" SHORTCUTURL="g"><img width="16" height="16" src="https://www.google.com/favicon.ico" style="margin-right: 0.5em;"/>Google</A><a name="Google" href="#Google" style="margin-left: 0.5em;">&para;</a>

        <DT><A HREF="javascript:(function(){var%20ca,cea,cs,df,dfe,i,j,x,y;function%20n(i,what){return%20i+%22%20%22+what+((i==1)?%22%22:%22s%22)}ca=cea=cs=0;df=document.forms;for(i=0;i<df.length;++i){x=df[i];dfe=x.elements;if(x.onsubmit){x.onsubmit=%22%22;++cs;}if(x.attributes[%22autocomplete%22]){x.attributes[%22autocomplete%22].value=%22on%22;++ca;}for(j=0;j<dfe.length;++j){y=dfe[j];if(y.attributes[%22autocomplete%22]){y.attributes[%22autocomplete%22].value=%22on%22;++cea;}}}alert(%22Removed%20autocomplete=off%20from%20%22+n(ca,%22form%22)+%22%20and%20from%20%22+n(cea,%22form%20element%22)+%22,%20and%20removed%20onsubmit%20from%20%22+n(cs,%22form%22)+%22.%20After%20you%20type%20your%20password%20and%20submit%20the%20form,%20the%20browser%20will%20offer%20to%20remember%20your%20password.%22)})();" name="javascript:(function(){var%20ca,cea,cs,df,dfe,i,j,x,y;function%20n(i,what){return%20i+%22%20%22+what+((i==1)?%22%22:%22s%22)}ca=cea=cs=0;df=document.forms;for(i=0;i<df.length;++i){x=df[i];dfe=x.elements;if(x.onsubmit){x.onsubmit=%22%22;++cs;}if(x.attributes[%22autocomplete%22]){x.attributes[%22autocomplete%22].value=%22on%22;++ca;}for(j=0;j<dfe.length;++j){y=dfe[j];if(y.attributes[%22autocomplete%22]){y.attributes[%22autocomplete%22].value=%22on%22;++cea;}}}alert(%22Removed%20autocomplete=off%20from%20%22+n(ca,%22form%22)+%22%20and%20from%20%22+n(cea,%22form%20element%22)+%22,%20and%20removed%20onsubmit%20from%20%22+n(cs,%22form%22)+%22.%20After%20you%20type%20your%20password%20and%20submit%20the%20form,%20the%20browser%20will%20offer%20to%20remember%20your%20password.%22)})();" ADD_DATE="1318292619" SHORTCUTURL="r"><img width="16" height="16" src="blank.gif" style="margin-right: 0.5em;"/>remember password</A><a name="remember password" href="#remember password" style="margin-left: 0.5em;">&para;</a>

        <HR>        <DT><A HREF="place:sort=14&type=6&maxResults=10&queryType=1" name="place:sort=14&type=6&maxResults=10&queryType=1"><img width="16" height="16" src="blank.gif" style="margin-right: 0.5em;"/>Recent Tags</A><a name="Recent Tags" href="#Recent Tags" style="margin-left: 0.5em;">&para;</a>

        <DT><A HREF="place:folder=BOOKMARKS_MENU&folder=UNFILED_BOOKMARKS&folder=TOOLBAR&sort=12&excludeQueries=1&maxResults=10&queryType=1" name="place:folder=BOOKMARKS_MENU&folder=UNFILED_BOOKMARKS&folder=TOOLBAR&sort=12&excludeQueries=1&maxResults=10&queryType=1"><img width="16" height="16" src="blank.gif" style="margin-right: 0.5em;"/>Recently Bookmarked</A><a name="Recently Bookmarked" href="#Recently Bookmarked" style="margin-left: 0.5em;">&para;</a>