Project

General

Profile

« Previous | Next » 

Revision 12440

Added by Aaron Marcuse-Kubitza almost 11 years ago

web/links/index.htm: updated to Firefox bookmarks: PostgreSQL: added explanation of the difference between STABLE and IMMUTABLE, and common pitfalls in using IMMUTABLE when you should use STABLE. svn: added troubleshooting steps for running `svn upgrade` after the last Mac system update, which upgrades svn.

View differences:

trunk/web/links/index.htm
834 834 
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/sql-createdomain.html" name="http://www.postgresql.org/docs/9.3/static/sql-createdomain.html" ADD_DATE="1386257057" 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: CREATE DOMAIN</A><a name="PostgreSQL: Documentation: 9.3: CREATE DOMAIN" href="#PostgreSQL: Documentation: 9.3: CREATE DOMAIN" style="margin-left: 0.5em;">&para;</a>
835 835 
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/runtime-config-logging.html#GUC-LOG-ERROR-VERBOSITY" name="http://www.postgresql.org/docs/9.3/static/runtime-config-logging.html#GUC-LOG-ERROR-VERBOSITY" ADD_DATE="1384823719" 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: Error Reporting and Logging</A><a name="PostgreSQL: Documentation: 9.3: Error Reporting and Logging" href="#PostgreSQL: Documentation: 9.3: Error Reporting and Logging" style="margin-left: 0.5em;">&para;</a>
836 836 
<DD>page's description: &#39;Valid values are TERSE, DEFAULT, and VERBOSE, each adding more fields to displayed messages. TERSE excludes the logging of DETAIL, HINT, QUERY, and CONTEXT error information. VERBOSE output includes the SQLSTATE error code (see also Appendix A) and the source code file name, function name, and line number that generated the error. Only superusers can change this setting [but it also exists in psql].&#39;
837 
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/interactive/xfunc-volatility.html" name="http://www.postgresql.org/docs/9.3/interactive/xfunc-volatility.html" ADD_DATE="1393355422" 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: Function Volatility Categories ***</A><a name="PostgreSQL: Documentation: 9.3: Function Volatility Categories ***" href="#PostgreSQL: Documentation: 9.3: Function Volatility Categories ***" style="margin-left: 0.5em;">&para;</a>
838 
<DD>-
839 
*** &quot;A common error is to label a function IMMUTABLE when its results depend on a configuration parameter. For example, a function that manipulates timestamps might well have results that depend on the TimeZone setting. For safety, such functions should be labeled STABLE instead.&quot;
840 
this especially includes functions that depend on the search_path!
841 

  		




  
  842
  
    
** &quot;There is relatively little difference between STABLE and IMMUTABLE categories when considering simple interactive queries that are planned and immediately executed: it doesn&#39;t matter a lot whether a function is executed once during planning or once during query execution startup. But there is a big difference if the plan is saved and reused later. Labeling a function IMMUTABLE when it really isn&#39;t might allow it to be prematurely folded to a constant during planning, resulting in a stale value being re-used during subsequent uses of the plan. This is a hazard when using prepared statements or when using function languages that cache plans (such as PL/pgSQL).&quot;


  		




  
  843
  
    
ie. if you are going to use your STABLE function in a PL/pgSQL function, be sure to label it STABLE so that it does not get constant-folded until call time (if labeled IMMUTABLE, it would be folded right away when the function is created)


  		




  
  844
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/functions-geometry.html" name="http://www.postgresql.org/docs/9.3/static/functions-geometry.html" ADD_DATE="1393319486" 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: Geometric Functions and Operators</A><a name="PostgreSQL: Documentation: 9.3: Geometric Functions and Operators" href="#PostgreSQL: Documentation: 9.3: Geometric Functions and Operators" style="margin-left: 0.5em;">&para;</a>


  		




  837
  845
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/app-pgdump.html" name="http://www.postgresql.org/docs/9.3/static/app-pgdump.html" ADD_DATE="1392338412" 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: pg_dump</A><a name="PostgreSQL: Documentation: 9.3: pg_dump" href="#PostgreSQL: Documentation: 9.3: pg_dump" style="margin-left: 0.5em;">&para;</a>


  		




  838
  846
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/pgupgrade.html" name="http://www.postgresql.org/docs/9.3/static/pgupgrade.html" ADD_DATE="1384429194" 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: pg_upgrade</A><a name="PostgreSQL: Documentation: 9.3: pg_upgrade" href="#PostgreSQL: Documentation: 9.3: pg_upgrade" style="margin-left: 0.5em;">&para;</a>


  		




  839
  847
  
    
                                <DT><A HREF="http://www.postgresql.org/docs/9.3/static/errcodes-appendix.html" name="http://www.postgresql.org/docs/9.3/static/errcodes-appendix.html" ADD_DATE="1392338775" ICON_URI="http://www.postgresql.org/favicon.ico"><img width="16" height="16" src="http://www.postgresql.org/favicon.ico" style="margin-right: 0.5em;"/>PostgreSQL: Documentation: 9.3: PostgreSQL Error Codes</A><a name="PostgreSQL: Documentation: 9.3: PostgreSQL Error Codes" href="#PostgreSQL: Documentation: 9.3: PostgreSQL Error Codes" style="margin-left: 0.5em;">&para;</a>


  		




  ......




  2248
  2256
  
    
            <DL><p>


  		




  2249
  2257
  
    
                <DT><a name="svn" href="#svn"><H3 ADD_DATE="1367370827">svn</H3></a>


  		




  2250
  2258
  
    
                <DL><p>


  		




  
  2259
  
    
                    <DT><A HREF="https://mail-archives.apache.org/mod_mbox/subversion-users/201204.mbox/%3CCAB84uBX14mkKsLD587-_RcUf-av3=G-Y0-chF1fKX1==qbT5Yg@mail.gmail.com%3E" name="https://mail-archives.apache.org/mod_mbox/subversion-users/201204.mbox/%3CCAB84uBX14mkKsLD587-_RcUf-av3=G-Y0-chF1fKX1==qbT5Yg@mail.gmail.com%3E" ADD_DATE="1393344356" ICON_URI="https://mail-archives.apache.org/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="https://mail-archives.apache.org/favicon.ico" style="margin-right: 0.5em;"/>&#39;svn upgrade&#39; fails with &quot;svn: E155016: Insufficient NODES rows&quot;</A><a name="&#39;svn upgrade&#39; fails with &quot;svn: E155016: Insufficient NODES rows&quot;" href="#&#39;svn upgrade&#39; fails with &quot;svn: E155016: Insufficient NODES rows&quot;" style="margin-left: 0.5em;">&para;</a>


  		




  
  2260
  
    
<DD>-


  		




  
  2261
  
    
a .*-revert file is indeed present, but deleting it does not fix the problem. instead, check out a new working copy:


  		




  
  2262
  
    
$ find . -name .svn -exec rm -rf {} \;


  		




  
  2263
  
    
$ svn co --force repo_url .


  		




  2251
  2264
  
    
                    <DT><A HREF="http://stackoverflow.com/questions/757435/how-to-escape-characters-in-subversion-managed-file-names" name="http://stackoverflow.com/questions/757435/how-to-escape-characters-in-subversion-managed-file-names" ADD_DATE="1390608592" ICON_URI="http://cdn.sstatic.net/stackoverflow/img/favicon.ico" LAST_CHARSET="UTF-8"><img width="16" height="16" src="http://cdn.sstatic.net/stackoverflow/img/favicon.ico" style="margin-right: 0.5em;"/>** svn - How to escape @ characters in Subversion managed file names? - Stack Overflow</A><a name="** svn - How to escape @ characters in Subversion managed file names? - Stack Overflow" href="#** svn - How to escape @ characters in Subversion managed file names? - Stack Overflow" style="margin-left: 0.5em;">&para;</a>


  		




  2252
  2265
  
    
<DD>&quot;You need only append an at sign to the end of the path [to escape any @s in it], such as news@11@. svn cares only about the last at sign in the argument, and it is not considered illegal to omit a literal peg revision specifier after that at sign&quot;


  		




  2253
  2266
  
    
note that the trailing-@ escape for paths containing @ should only be used on paths where @ has a special meaning (usually only the *input* path)


  		












Also available in:  Unified diff