Server IP : 103.119.228.120 / Your IP : 18.191.129.241 Web Server : Apache System : Linux v8.techscape8.com 3.10.0-1160.119.1.el7.tuxcare.els2.x86_64 #1 SMP Mon Jul 15 12:09:18 UTC 2024 x86_64 User : nobody ( 99) PHP Version : 5.6.40 Disable Function : shell_exec,symlink,system,exec,proc_get_status,proc_nice,proc_terminate,define_syslog_variables,syslog,openlog,closelog,escapeshellcmd,passthru,ocinum cols,ini_alter,leak,listen,chgrp,apache_note,apache_setenv,debugger_on,debugger_off,ftp_exec,dl,dll,myshellexec,proc_open,socket_bind,proc_close,escapeshellarg,parse_ini_filepopen,fpassthru,exec,passthru,escapeshellarg,escapeshellcmd,proc_close,proc_open,ini_alter,popen,show_source,proc_nice,proc_terminate,proc_get_status,proc_close,pfsockopen,leak,apache_child_terminate,posix_kill,posix_mkfifo,posix_setpgid,posix_setsid,posix_setuid,dl,symlink,shell_exec,system,dl,passthru,escapeshellarg,escapeshellcmd,myshellexec,c99_buff_prepare,c99_sess_put,fpassthru,getdisfunc,fx29exec,fx29exec2,is_windows,disp_freespace,fx29sh_getupdate,fx29_buff_prepare,fx29_sess_put,fx29shexit,fx29fsearch,fx29ftpbrutecheck,fx29sh_tools,fx29sh_about,milw0rm,imagez,sh_name,myshellexec,checkproxyhost,dosyayicek,c99_buff_prepare,c99_sess_put,c99getsource,c99sh_getupdate,c99fsearch,c99shexit,view_perms,posix_getpwuid,posix_getgrgid,posix_kill,parse_perms,parsesort,view_perms_color,set_encoder_input,ls_setcheckboxall,ls_reverse_all,rsg_read,rsg_glob,selfURL,dispsecinfo,unix2DosTime,addFile,system,get_users,view_size,DirFiles,DirFilesWide,DirPrintHTMLHeaders,GetFilesTotal,GetTitles,GetTimeTotal,GetMatchesCount,GetFileMatchesCount,GetResultFiles,fs_copy_dir,fs_copy_obj,fs_move_dir,fs_move_obj,fs_rmdir,SearchText,getmicrotime MySQL : ON | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /usr/local/ssl/local/ssl/share/doc/postgresql-9.2.24/html/ |
Upload File : |
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML ><HEAD ><TITLE >Release 8.3.1</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK REV="MADE" HREF="mailto:pgsql-docs@postgresql.org"><LINK REL="HOME" TITLE="PostgreSQL 9.2.24 Documentation" HREF="index.html"><LINK REL="UP" TITLE="Release Notes" HREF="release.html"><LINK REL="PREVIOUS" TITLE="Release 8.3.2" HREF="release-8-3-2.html"><LINK REL="NEXT" TITLE="Release 8.3" HREF="release-8-3.html"><LINK REL="STYLESHEET" TYPE="text/css" HREF="stylesheet.css"><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"><META NAME="creation" CONTENT="2017-11-06T22:43:11"></HEAD ><BODY CLASS="SECT1" ><DIV CLASS="NAVHEADER" ><TABLE SUMMARY="Header navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TH COLSPAN="5" ALIGN="center" VALIGN="bottom" ><A HREF="index.html" >PostgreSQL 9.2.24 Documentation</A ></TH ></TR ><TR ><TD WIDTH="10%" ALIGN="left" VALIGN="top" ><A TITLE="Release 8.3.2" HREF="release-8-3-2.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="10%" ALIGN="left" VALIGN="top" ><A HREF="release.html" ACCESSKEY="U" >Up</A ></TD ><TD WIDTH="60%" ALIGN="center" VALIGN="bottom" >Appendix E. Release Notes</TD ><TD WIDTH="20%" ALIGN="right" VALIGN="top" ><A TITLE="Release 8.3" HREF="release-8-3.html" ACCESSKEY="N" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A NAME="RELEASE-8-3-1" >E.120. Release 8.3.1</A ></H1 ><DIV CLASS="FORMALPARA" ><P ><B >Release date: </B >2008-03-17</P ></DIV ><P > This release contains a variety of fixes from 8.3.0. For information about new features in the 8.3 major release, see <A HREF="release-8-3.html" >Section E.121</A >. </P ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AEN131211" >E.120.1. Migration to Version 8.3.1</A ></H2 ><P > A dump/restore is not required for those running 8.3.X. However, you might need to <TT CLASS="COMMAND" >REINDEX</TT > indexes on textual columns after updating, if you are affected by the Windows locale issue described below. </P ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="AEN131215" >E.120.2. Changes</A ></H2 ><P ></P ><UL ><LI ><P > Fix character string comparison for Windows locales that consider different character combinations as equal (Tom) </P ><P > This fix applies only on Windows and only when using UTF-8 database encoding. The same fix was made for all other cases over two years ago, but Windows with UTF-8 uses a separate code path that was not updated. If you are using a locale that considers some non-identical strings as equal, you may need to <TT CLASS="COMMAND" >REINDEX</TT > to fix existing indexes on textual columns. </P ></LI ><LI ><P > Repair corner-case bugs in <TT CLASS="COMMAND" >VACUUM FULL</TT > (Tom) </P ><P > A potential deadlock between concurrent <TT CLASS="COMMAND" >VACUUM FULL</TT > operations on different system catalogs was introduced in 8.2. This has now been corrected. 8.3 made this worse because the deadlock could occur within a critical code section, making it a PANIC rather than just ERROR condition. </P ><P > Also, a <TT CLASS="COMMAND" >VACUUM FULL</TT > that failed partway through vacuuming a system catalog could result in cache corruption in concurrent database sessions. </P ><P > Another <TT CLASS="COMMAND" >VACUUM FULL</TT > bug introduced in 8.3 could result in a crash or out-of-memory report when dealing with pages containing no live tuples. </P ></LI ><LI ><P > Fix misbehavior of foreign key checks involving <TT CLASS="TYPE" >character</TT > or <TT CLASS="TYPE" >bit</TT > columns (Tom) </P ><P > If the referencing column were of a different but compatible type (for instance <TT CLASS="TYPE" >varchar</TT >), the constraint was enforced incorrectly. </P ></LI ><LI ><P > Avoid needless deadlock failures in no-op foreign-key checks (Stephan Szabo, Tom) </P ></LI ><LI ><P > Fix possible core dump when re-planning a prepared query (Tom) </P ><P > This bug affected only protocol-level prepare operations, not SQL <TT CLASS="COMMAND" >PREPARE</TT >, and so tended to be seen only with JDBC, DBI, and other client-side drivers that use prepared statements heavily. </P ></LI ><LI ><P > Fix possible failure when re-planning a query that calls an SPI-using function (Tom) </P ></LI ><LI ><P > Fix failure in row-wise comparisons involving columns of different datatypes (Tom) </P ></LI ><LI ><P > Fix longstanding <TT CLASS="COMMAND" >LISTEN</TT >/<TT CLASS="COMMAND" >NOTIFY</TT > race condition (Tom) </P ><P > In rare cases a session that had just executed a <TT CLASS="COMMAND" >LISTEN</TT > might not get a notification, even though one would be expected because the concurrent transaction executing <TT CLASS="COMMAND" >NOTIFY</TT > was observed to commit later. </P ><P > A side effect of the fix is that a transaction that has executed a not-yet-committed <TT CLASS="COMMAND" >LISTEN</TT > command will not see any row in <TT CLASS="STRUCTNAME" >pg_listener</TT > for the <TT CLASS="COMMAND" >LISTEN</TT >, should it choose to look; formerly it would have. This behavior was never documented one way or the other, but it is possible that some applications depend on the old behavior. </P ></LI ><LI ><P > Disallow <TT CLASS="COMMAND" >LISTEN</TT > and <TT CLASS="COMMAND" >UNLISTEN</TT > within a prepared transaction (Tom) </P ><P > This was formerly allowed but trying to do it had various unpleasant consequences, notably that the originating backend could not exit as long as an <TT CLASS="COMMAND" >UNLISTEN</TT > remained uncommitted. </P ></LI ><LI ><P > Disallow dropping a temporary table within a prepared transaction (Heikki) </P ><P > This was correctly disallowed by 8.1, but the check was inadvertently broken in 8.2 and 8.3. </P ></LI ><LI ><P > Fix rare crash when an error occurs during a query using a hash index (Heikki) </P ></LI ><LI ><P > Fix incorrect comparison of <TT CLASS="TYPE" >tsquery</TT > values (Teodor) </P ></LI ><LI ><P > Fix incorrect behavior of <TT CLASS="LITERAL" >LIKE</TT > with non-ASCII characters in single-byte encodings (Rolf Jentsch) </P ></LI ><LI ><P > Disable <CODE CLASS="FUNCTION" >xmlvalidate</CODE > (Tom) </P ><P > This function should have been removed before 8.3 release, but was inadvertently left in the source code. It poses a small security risk since unprivileged users could use it to read the first few characters of any file accessible to the server. </P ></LI ><LI ><P > Fix memory leaks in certain usages of set-returning functions (Neil) </P ></LI ><LI ><P > Make <CODE CLASS="FUNCTION" >encode(<TT CLASS="REPLACEABLE" ><I >bytea</I ></TT >, 'escape')</CODE > convert all high-bit-set byte values into <TT CLASS="LITERAL" >\</TT ><TT CLASS="REPLACEABLE" ><I >nnn</I ></TT > octal escape sequences (Tom) </P ><P > This is necessary to avoid encoding problems when the database encoding is multi-byte. This change could pose compatibility issues for applications that are expecting specific results from <CODE CLASS="FUNCTION" >encode</CODE >. </P ></LI ><LI ><P > Fix input of datetime values for February 29 in years BC (Tom) </P ><P > The former coding was mistaken about which years were leap years. </P ></LI ><LI ><P > Fix <SPAN CLASS="QUOTE" >"unrecognized node type"</SPAN > error in some variants of <TT CLASS="COMMAND" >ALTER OWNER</TT > (Tom) </P ></LI ><LI ><P > Avoid tablespace permissions errors in <TT CLASS="COMMAND" >CREATE TABLE LIKE INCLUDING INDEXES</TT > (Tom) </P ></LI ><LI ><P > Ensure <TT CLASS="STRUCTNAME" >pg_stat_activity</TT >.<TT CLASS="STRUCTFIELD" >waiting</TT > flag is cleared when a lock wait is aborted (Tom) </P ></LI ><LI ><P > Fix handling of process permissions on Windows Vista (Dave, Magnus) </P ><P > In particular, this fix allows starting the server as the Administrator user. </P ></LI ><LI ><P > Update time zone data files to <SPAN CLASS="APPLICATION" >tzdata</SPAN > release 2008a (in particular, recent Chile changes); adjust timezone abbreviation <TT CLASS="LITERAL" >VET</TT > (Venezuela) to mean UTC-4:30, not UTC-4:00 (Tom) </P ></LI ><LI ><P > Fix <SPAN CLASS="APPLICATION" >ecpg</SPAN > problems with arrays (Michael) </P ></LI ><LI ><P > Fix <SPAN CLASS="APPLICATION" >pg_ctl</SPAN > to correctly extract the postmaster's port number from command-line options (Itagaki Takahiro, Tom) </P ><P > Previously, <TT CLASS="LITERAL" >pg_ctl start -w</TT > could try to contact the postmaster on the wrong port, leading to bogus reports of startup failure. </P ></LI ><LI ><P > Use <TT CLASS="OPTION" >-fwrapv</TT > to defend against possible misoptimization in recent <SPAN CLASS="APPLICATION" >gcc</SPAN > versions (Tom) </P ><P > This is known to be necessary when building <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > with <SPAN CLASS="APPLICATION" >gcc</SPAN > 4.3 or later. </P ></LI ><LI ><P > Enable building <TT CLASS="FILENAME" >contrib/uuid-ossp</TT > with MSVC (Hiroshi Saito) </P ></LI ></UL ></DIV ></DIV ><DIV CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE SUMMARY="Footer navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="release-8-3-2.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="index.html" ACCESSKEY="H" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" ><A HREF="release-8-3.html" ACCESSKEY="N" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >Release 8.3.2</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="release.html" ACCESSKEY="U" >Up</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" >Release 8.3</TD ></TR ></TABLE ></DIV ></BODY ></HTML >