Server IP : 103.119.228.120 / Your IP : 18.220.200.33 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/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 >Implementation</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="GIN Indexes" HREF="gin.html"><LINK REL="PREVIOUS" TITLE="Extensibility" HREF="gin-extensibility.html"><LINK REL="NEXT" TITLE="GIN Tips and Tricks" HREF="gin-tips.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="Extensibility" HREF="gin-extensibility.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="10%" ALIGN="left" VALIGN="top" ><A HREF="gin.html" ACCESSKEY="U" >Up</A ></TD ><TD WIDTH="60%" ALIGN="center" VALIGN="bottom" >Chapter 55. GIN Indexes</TD ><TD WIDTH="20%" ALIGN="right" VALIGN="top" ><A TITLE="GIN Tips and Tricks" HREF="gin-tips.html" ACCESSKEY="N" >Next</A ></TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A NAME="GIN-IMPLEMENTATION" >55.3. Implementation</A ></H1 ><P > Internally, a <ACRONYM CLASS="ACRONYM" >GIN</ACRONYM > index contains a B-tree index constructed over keys, where each key is an element of one or more indexed items (a member of an array, for example) and where each tuple in a leaf page contains either a pointer to a B-tree of heap pointers (a <SPAN CLASS="QUOTE" >"posting tree"</SPAN >), or a simple list of heap pointers (a <SPAN CLASS="QUOTE" >"posting list"</SPAN >) when the list is small enough to fit into a single index tuple along with the key value. </P ><P > As of <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > 9.1, NULL key values can be included in the index. Also, placeholder NULLs are included in the index for indexed items that are NULL or contain no keys according to <CODE CLASS="FUNCTION" >extractValue</CODE >. This allows searches that should find empty items to do so. </P ><P > Multicolumn <ACRONYM CLASS="ACRONYM" >GIN</ACRONYM > indexes are implemented by building a single B-tree over composite values (column number, key value). The key values for different columns can be of different types. </P ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="GIN-FAST-UPDATE" >55.3.1. GIN Fast Update Technique</A ></H2 ><P > Updating a <ACRONYM CLASS="ACRONYM" >GIN</ACRONYM > index tends to be slow because of the intrinsic nature of inverted indexes: inserting or updating one heap row can cause many inserts into the index (one for each key extracted from the indexed item). As of <SPAN CLASS="PRODUCTNAME" >PostgreSQL</SPAN > 8.4, <ACRONYM CLASS="ACRONYM" >GIN</ACRONYM > is capable of postponing much of this work by inserting new tuples into a temporary, unsorted list of pending entries. When the table is vacuumed, or if the pending list becomes too large (larger than <A HREF="runtime-config-resource.html#GUC-WORK-MEM" >work_mem</A >), the entries are moved to the main <ACRONYM CLASS="ACRONYM" >GIN</ACRONYM > data structure using the same bulk insert techniques used during initial index creation. This greatly improves <ACRONYM CLASS="ACRONYM" >GIN</ACRONYM > index update speed, even counting the additional vacuum overhead. Moreover the overhead work can be done by a background process instead of in foreground query processing. </P ><P > The main disadvantage of this approach is that searches must scan the list of pending entries in addition to searching the regular index, and so a large list of pending entries will slow searches significantly. Another disadvantage is that, while most updates are fast, an update that causes the pending list to become <SPAN CLASS="QUOTE" >"too large"</SPAN > will incur an immediate cleanup cycle and thus be much slower than other updates. Proper use of autovacuum can minimize both of these problems. </P ><P > If consistent response time is more important than update speed, use of pending entries can be disabled by turning off the <TT CLASS="LITERAL" >FASTUPDATE</TT > storage parameter for a <ACRONYM CLASS="ACRONYM" >GIN</ACRONYM > index. See <A HREF="sql-createindex.html" >CREATE INDEX</A > for details. </P ></DIV ><DIV CLASS="SECT2" ><H2 CLASS="SECT2" ><A NAME="GIN-PARTIAL-MATCH" >55.3.2. Partial Match Algorithm</A ></H2 ><P > GIN can support <SPAN CLASS="QUOTE" >"partial match"</SPAN > queries, in which the query does not determine an exact match for one or more keys, but the possible matches fall within a reasonably narrow range of key values (within the key sorting order determined by the <CODE CLASS="FUNCTION" >compare</CODE > support method). The <CODE CLASS="FUNCTION" >extractQuery</CODE > method, instead of returning a key value to be matched exactly, returns a key value that is the lower bound of the range to be searched, and sets the <TT CLASS="LITERAL" >pmatch</TT > flag true. The key range is then scanned using the <CODE CLASS="FUNCTION" >comparePartial</CODE > method. <CODE CLASS="FUNCTION" >comparePartial</CODE > must return zero for a matching index key, less than zero for a non-match that is still within the range to be searched, or greater than zero if the index key is past the range that could match. </P ></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="gin-extensibility.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="gin-tips.html" ACCESSKEY="N" >Next</A ></TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >Extensibility</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="gin.html" ACCESSKEY="U" >Up</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" >GIN Tips and Tricks</TD ></TR ></TABLE ></DIV ></BODY ></HTML >