Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Tue Feb 6 22:16:17 EST 2007
+ Last updated: Wed Apr 18 23:05:05 EDT 2007
Current maintainer: Bruce Momjian (bruce@momjian.us)
1.6) What is the most recent release?
- The latest release of PostgreSQL is version 8.2.3.
+ The latest release of PostgreSQL is version 8.2.4.
We plan to have a major release every year, with minor releases every
few months.
3.6) What is the upgrade process for PostgreSQL?
- The PostgreSQL team makes only bug fixes in minor releases, so, for
- example, upgrading from 7.4.8 to 7.4.9 does not require a dump and
- restore; merely stop the database server, install the updated
- binaries, and restart the server.
-
- All users should upgrade to the most recent minor release as soon as
- it is available. While every upgrade has some risk, PostgreSQL minor
- releases are designed to fix only common bugs with the least risk. The
- community considers not upgrading more risky that upgrading.
-
- Major releases (e.g. from 7.3 to 7.4) often change the internal format
- of system tables and data files. These changes are often complex, so
- we don't maintain backward compatibility for data files. A dump/reload
- of the database is required for major upgrades.
+ See http://www.postgresql.org/support/versioning.
3.7) What computer hardware should I use?
As an example, consider a file of 100,000 lines with an integer and
text description on each line. Suppose the text string avergages
twenty bytes in length. The flat file would be 2.8 MB. The size of the
- PostgreSQL database file containing this data can be estimated as 5.6
+ PostgreSQL database file containing this data can be estimated as 5.2
MB:
- 28 bytes: each row header (approximate)
+ 24 bytes: each row header (approximate)
24 bytes: one int field and one text field
+ 4 bytes: pointer on page to tuple
----------------------------------------
- 56 bytes per row
+ 52 bytes per row
The data page size in PostgreSQL is 8192 bytes (8 KB), so:
8192 bytes per page
- ------------------- = 146 rows per database page (rounded down)
- 56 bytes per row
+ ------------------- = 158 rows per database page (rounded down)
+ 52 bytes per row
100000 data rows
- -------------------- = 685 database pages (rounded up)
- 146 rows per page
+ -------------------- = 633 database pages (rounded up)
+ 158 rows per page
-685 database pages * 8192 bytes per page = 5,611,520 bytes (5.6 MB)
+633 database pages * 8192 bytes per page = 5,185,536 bytes (5.2 MB)
Indexes do not require as much overhead, but do contain the data that
is being indexed, so they can be large also.
4.18) How do I return multiple rows or columns from a function?
It is easy using set-returning functions,
- http://techdocs.postgresql.org/guides/SetReturningFunctions
+ http://www.postgresql.org/docs/techdocs.17
.
4.19) Why do I get "relation with OID ##### does not exist" errors when
AIX Specific
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
=======================================================
-Last updated: $Date: 2007/02/07 03:16:59 $
+Last updated: $Date: 2007/04/19 03:07:22 $
Topics
-----
From: Zeugswetter Andreas <ZeugswetterA@spardat.at>
-$Date: 2007/02/07 03:16:59 $
+$Date: 2007/04/19 03:07:22 $
On AIX 4.3.2 PostgreSQL compiled with the native IBM compiler xlc
(vac.C 5.0.1) passes all regression tests. Other versions of OS and
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Thu Jan 4 16:00:00 EST 2007
+ Last updated: Mon Mar 19 12:52:30 EDT 2007
Current maintainer: Bruce Momjian (bruce@momjian.us)
1.16) Where can I get a copy of the SQL standards?
1.17) Where can I get technical assistance?
1.18) How do I get involved in PostgreSQL web site development?
- 1.19) What is the timeline for the next major PostgreSQL release?
+ 1.19) Why haven't you replaced CVS with SVN, Git, Monotone, VSS,
+ <insert your favorite SCM system here>?
Technical Questions
Some developers use compilers from other software vendors with mixed
results.
- Developers who are regularly rebuilding the source often pass the
+ Developers who regularly rebuild the source often pass the
--enable-depend flag to configure. The result is that when you make a
modification to a C header file, all files depend upon that file are
also rebuilt.
+ src/Makefile.custom can be used to set environment variables, like
+ CUSTOM_COPT, that are used for every compile.
+
1.3) What areas need work?
Outstanding features are detailed in the TODO list. This is located in
src/tools/make_diff/difforig useful. (Unified diffs are only
preferable if the file changes are single-line changes and do not
rely on surrounding lines.)
- 4. PostgreSQL is licensed under a BSD license, so any submissions
- must conform to the BSD license to be included. If you use code
- that is available under some other license that is BSD compatible
- (eg. public domain) please note that code in your email submission
+ 4. PostgreSQL is licensed under a BSD license. By posting a patch to
+ the public PostgreSQL mailling lists, you are giving the
+ PostgreSQL Global Development Group the non-revokable right to
+ distribute your patch under the BSD license.
5. Confirm that your changes can pass the regression tests. If your
changes are port specific, please list the ports you have tested
it on.
- 6. Provide an implementation overview, preferably in code comments.
- Following the surrounding code commenting style is usually a good
- approach.
+ 6. If you are adding a new feature, confirm that it has been tested
+ thoroughly. Try to test the feature in all conceivable scenarios.
7. New feature patches should also be accompanied by documentation
patches. If you need help checking the SQL standard, see 1.16.
- 8. If you are adding a new feature, confirm that it has been tested
- thoroughly. Try to test the feature in all conceivable scenarios.
+ 8. Provide an implementation overview, preferably in code comments.
+ Following the surrounding code commenting style is usually a good
+ approach.
9. If it is a performance patch, please provide confirming test
results to show the benefit of your patch. It is OK to post
patches without this information, though the patch will not be
http://gborg.postgresql.org/project/pgweb/projdisplay.php , the code
for the next version of the website is under the "portal" module.
+ 1.19) Why haven't you replaced CVS with SVN, Git, Monotone, VSS, <insert your
+ favorite SCMS here>?
+
+ Currently the core developers see no SCMS that will provide enough
+ benefit to outwiegh the pain involved in moving to a new SCMS. Typical
+ problems that must be addressed by any new SCMS include:
+ * Run natively on all of our supported platforms.
+ * Integrate into the Buildfarm.
+ * Import our entire CVS Repository while preserving complete
+ history.
+ * Allow for anonymous checkouts.
+
+ Currently there is no intention for switching to a new SCMS until at
+ least the end of the 8.4 development cycle sometime in late 2008. For
+ more information please refer to the mailing list archives.
+
Technical Questions
2.1) How do I efficiently access information in tables from the backend code?
pgsql/data directory. The client profile file will be put in the
client's current directory. Linux requires a compile with
-DLINUX_PROFILE for proper profiling.
-
- 2.9) What is the timeline for the next major PostgreSQL release?
-
- The development schedule for the 8.3 release is:
-
- March 1, 2007
-
- Initial community review of all major feature patches
- April 1, 2007
-
- Feature freeze, all patches must be submitted for review and
- application
- mid-May, 2007
-
- All patches applied, beta testing begins
- July, 2007
-
- Release of 8.3.0
-
- Patches that appear after appropriate dates are typically not applied
- but held for the next major release.
HP-UX Specific
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
=======================================================
-last updated: $Date: 2007/02/07 03:16:59 $
+last updated: $Date: 2007/04/19 03:07:22 $
current maintainer: Tom Lane (tgl@sss.pgh.pa.us)
original author: Tom Lane (tgl@sss.pgh.pa.us)
IRIX Specific
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
=======================================================
-last updated: $Date: 2007/02/07 03:16:59 $
+last updated: $Date: 2007/04/19 03:07:22 $
current maintainer: Luis Amigo (lamigo@atc.unican.es)
original author: Luis Amigo (lamigo@atc.unican.es)
IRIX Specific
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
=======================================================
-last updated: $Date: 2007/02/07 03:16:59 $
+last updated: $Date: 2007/04/19 03:07:22 $
current maintainer: Billy G. Allie (Bill.Allie@mug.org)
original author: Andrew Merrill (andrew@compclass.com)
Sun Solaris specific
To be read in conjunction with the installation instructions.
============================================================
-Last updated: $Date: 2007/02/07 03:16:59 $
+Last updated: $Date: 2007/04/19 03:07:22 $
Contents:
This is probably a case of the run-time linker being unable to find
some library, probably libz, libreadline or some other non-standard
library such as libssl. To point it to the right location, set the
-LD_LIBRARY_PATH environment variable, e.g.,
+LDFLAGS environment variable, e.g.,
- LD_LIBRARY_PATH=/usr/sfw/lib:/opt/sfw/lib:/usr/local/lib
- export LD_LIBRARY_PATH
+ LDFLAGS="-R /usr/sfw/lib:/opt/sfw/lib:/usr/local/lib"
+ export LDFLAGS
-and restart configure. You will also have to keep this setting whenever
-you run any of the installed PostgreSQL programs. Alternatively, set
-the environment variable LD_RUN_PATH. See the ld(1) man page for more
+and restart configure. See the ld(1) man page for more
information.
Yes, see the chapter "Monitoring Database Activity" in the documentation
for further information.
+You can also find more information here:
+
+ http://blogs.sun.com/robertlor/entry/user_level_dtrace_probes_in
+
If you see the linking of the postgres executable abort with an error
message like
gmake: *** [postgres] Error 1
your DTrace installation is too old to handle probes in static
-functions. You need Solaris 10u3 or newer.
+functions. You need Solaris 10u4 or newer. Workaround is remove static
+keyword from AbortTransaction and CommitTransaction functions declaration in
+src/backend/access/transam/xact.c.
-You can also find more information here:
-
- http://blogs.sun.com/robertlor/entry/user_level_dtrace_probes_in
+See http://sunsolve.sun.com/search/document.do?assetkey=1-1-2139224-1
+(registration required).
1.13) Wie sende ich einen Fehlerbericht?
Bitte besuchen Sie die PostgreSQL-BugTool-Seite
- http://www.postgresql.org/bugform.html, die Hinweise und Anleitungen
- zur Einreichung von Fehlerberichten enthält.
+ http://www.postgresql.org/support/submitbug, die Hinweise und
+ Anleitungen zur Einreichung von Fehlerberichten enthält.
Überprüfe auch den ftp-Server ftp://ftp.postgresql.org/pub/, um
nachzusehen, ob es eine neuere PostgreSQL-Version oder neue Patches
PostgreSQL(¥Ý¥¹¥È¥°¥ì¥¹¡¦¥¥å¡¼¡¦¥¨¥ë)¤Ë¤Ä¤¤¤Æ¤è¤¯¤¢¤ë¼ÁÌä¤È¤½¤Î²òÅú(FAQ)
-¸¶Ê¸ºÇ½ª¹¹¿·Æü: Mon Dec 11 17:45:54 EST 2006
+¸¶Ê¸ºÇ½ª¹¹¿·Æü: Tue Mar 20 13:43:40 EDT 2007
¸½ºß¤Î°Ý»ý´ÉÍý¼Ô: Bruce Momjian (bruce@momjian.us)
Maintainer of Japanese Translation: Jun Kuwamura (juk at PostgreSQL.jp)
1.11) SQL¤Ï¤É¤¦¤¹¤ì¤Ð³Ø¤Ù¤Þ¤¹¤«¡©
1.12) ¥Ñ¥Ã¥Á¤òÄ󶡤·¤¿¤ê¡¢³«È¯¥Á¡¼¥à»²²Ã¤¹¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤è¤¤¤Ç¤¹¤«¡©
1.13) ¾¤ÎDBMS¤ÈÈæ¤Ù¤ÆPostgreSQL¤Ï¤É¤¦¤Ê¤Î¤Ç¤¹¤«¡©
+1.14) PostgreSQL¤Ï¹ñËè¤ÎºÇ¿·¤Î²Æ»þ´Ö¤ÎÊѹ¹¤ò°·¤¤¤Þ¤¹¤«¡©
¥æ¡¼¥¶¡¦¥¯¥é¥¤¥¢¥ó¥È¤Î¼ÁÌä
¡©
3.4) ¤É¤Î¤è¤¦¤Ê¥Ç¥Ð¥°µ¡Ç½¤¬»È¤¨¤Þ¤¹¤«¡©
3.5) Àܳ¤·¤è¤¦¤È¤¹¤ë¤È¤¤Ë 'Sorry, too many clients' ¤¬½Ð¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©
-3.6) PostgreSQL¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¼ê½ç¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©
-3.7) ¥Ï¡¼¥É¥¦¥§¥¢¤Ë¤Ï¤É¤ó¤Ê¥³¥ó¥Ô¥å¡¼¥¿¤ò»È¤¨¤Ð¤è¤¤¤Ç¤¹¤«¡©
+3.6) PostgreSQL¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¼ê½ç¤Ï¤É¤¦¤Ê¤ê¤Þ¤¹¤«¡©
+3.7) ¥Ï¡¼¥É¥¦¥§¥¢¤Ë¤Ï¤É¤Τ褦¤Ê¥³¥ó¥Ô¥å¡¼¥¿¤ò»È¤¨¤Ð¤è¤¤¤Ç¤¹¤«¡©
Áàºî¾å¤Î¼ÁÌä
POSTGRESQL ¥Ç¡¼¥¿¥Ù¡¼¥¹´ÉÍý¥·¥¹¥Æ¥à
- ÉôʬŪÃøºî¸¢ (c) 1996-2006, PostgreSQL¹ñºÝ³«È¯¥Á¡¼¥à
+ ÉôʬŪÃøºî¸¢ (c) 1996-2007, PostgreSQL¹ñºÝ³«È¯¥Á¡¼¥à
ÉôʬŪÃøºî¸¢ (c) 1994-1996 ¥«¥ê¥Õ¥©¥ë¥Ë¥¢Âç³ØËܹ»
1.6) ºÇ¿·¤Î¥ê¥ê¡¼¥¹¤Ï¤É¤ì¤Ç¤¹¤«¡©
-PostgreSQL ¤ÎºÇ¿·ÈǤϥС¼¥¸¥ç¥ó 8.2.0 ¤Ç¤¹¡£
+PostgreSQL ¤ÎºÇ¿·ÈǤϥС¼¥¸¥ç¥ó 8.2.3 ¤Ç¤¹¡£
²æ¡¹¤Ï¡¢1ǯËè¤Ë¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¤ò¡¢¿ô¥õ·î¤´¤È¤Î¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤ò¹Ô¤Ê¤¦¤³¤È¤ò·×
²è¤·¤Æ¤¤¤Þ¤¹¡£
¥¹¥¿¥¤¥ë¤Î»ÈÍѵöÂú¤Ë³°¤ì¤Ê¤¤¸Â¤ê¡¢PostgreSQL¤Î¥³¡¼¥É¤òÀ©¸Â̵¤·¤Ç¾¦ÉʤËÁȤß
¹þ¤à¤³¤È¤¬¤Ç¤¤Þ¤¹¡£
+1.14) PostgreSQL¤Ï¹ñËè¤ÎºÇ¿·¤Î²Æ»þ´Ö¤ÎÊѹ¹¤ò°·¤¤¤Þ¤¹¤«¡©
+
+¹ç½£¹ñ¤Î²Æ»þ´Ö¤ÎÊѹ¹¤Ï¡¢PostgreSQL¤Î¥ê¥ê¡¼¥¹8.0.4°Ê¹ß[4+]¤È¡¢¤½¤Î¸å¤Î¥á¥¸¥ã¡¼¥ê
+¥ê¡¼¥¹¡¢¤¿¤È¤¨¤Ð 8.1 ¤Ë¤Ï´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£¥«¥Ê¥À¤È¥ª¡¼À¾Éô¥¹¥È¥é¥ê¥¢¤ÎÊѹ¹¤Ï¡¢
+8.0.[10+], 8.1.[6+] ¤ª¤è¤Ó¡¢¤½¤Î¸å¤Î¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¤Î¤¹¤Ù¤Æ¤Ë´Þ¤Þ¤ì¤Þ¤¹¡£8.0¤è
+¤êÁ°¤ÎPosrgreSQL¤Ç¤Ï¥ª¥Ú¥ì¡¼¥Æ¥£¥ó¥°¥·¥¹¥Æ¥à¤Î¥¿¥¤¥à¥¾¡¼¥ó¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò²Æ»þ´Ö
+¾ðÊó¤Î¤¿¤á¤Ë»È¤Ã¤Æ¤¤¤Þ¤¹¡£
+
¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬¨¬
¥æ¡¼¥¶¡¦¥¯¥é¥¤¥¢¥ó¥È¤Î¼ÁÌä
postgresql.conf ¤ÎÃæ¤Î max_connections ¤ÎÃͤòÊѹ¹¤·¤Æ postmaster¤òºÆµ¯Æ°¤¹¤ë¤³
¤È¤Ç²Äǽ¤Ë¤Ê¤ê¤Þ¤¹¡£
-3.6) PostgreSQL¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¼ê½ç¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©
+3.6) PostgreSQL¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¼ê½ç¤Ï¤É¤¦¤Ê¤ê¤Þ¤¹¤«¡©
+
+¥Ð¡¼¥¸¥ç¥óÈÖ¹æÉÕ¤±¤ÎÊý¿Ë¤Ë¤Ä¤¤¤Æ¤Ï¡¢http://www.postgresql.org/support/
+versioning ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
-PostgreSQL¥Á¡¼¥à¤Ï¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Ç¤Ï¥Ð¥°¤Î½¤Àµ¤·¤«¹Ô¤Ê¤¤¤Þ¤»¤ó¤Î¤Ç¡¢¤¿¤È¤¨¤Ð
-7.4.8 ¤«¤é 7.4.9 ¤Ø¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ë¥À¥ó¥×¤È¥ê¥¹¥È¥¢¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£¤·¤¿¤¬¤Ã
-¤Æ¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¥µ¡¼¥Ð¤ò°ì»þŪ¤ËÄä»ß¤·¤Æ¡¢¥¢¥Ã¥×¥Ç¡¼¥È¤·¤¿¥Ð¥¤¥Ê¥ê¤ò¥¤¥ó¥¹¥È¡¼
-¥ë¤·¡¢¤½¤·¤Æ¡¢¥µ¡¼¥Ð¤ò¥ê¥¹¥¿¡¼¥È¤¹¤ë¤À¤±¤Ç¤¹¡£
+¿·¤·¤¤µ¡Ç½¤òÀ¹¤ê¹þ¤àPostgreSQL¤Î¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¤Ï¤À¤¤¤¿¤¤Ç¯¤Ë1²óÄøÅٹԤʤ¤¤Þ¤¹
+¡£¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¤Ï¡¢¤¿¤È¤¨¤Ð¡¢8.1¤«¤é8.2¤Ø¤Î¤è¤¦¤Ë¡¢¥Ð¡¼¥¸¥ç¥óÈÖ¹æ¤Î1ÈÖÌܤ«2
+ÈÖÌܤÎÉôʬ¤òÁý¤ä¤·¤Æ¤æ¤¤Þ¤¹¡£
-Á´¥æ¡¼¥¶¤Ï¤Ç¤¤ë¤À¤±Á᤯ºÇ¿·¤Î¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë¤Ù¤¤Ç¤¹¡£¤¹
-¤Ù¤Æ¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ë¥ê¥¹¥¯¤Ï¤Ä¤¤â¤Î¤Ç¤¹¤¬¡¢ PostgreSQL¤Î¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Ï¡¢
-¤Ê¤ë¤Ù¤¯¾®¤µ¤Ê¥ê¥¹¥¯¤Ç°ìÈÌŪ¤Ê¥Ð¥°¤Î½¤Àµ¤À¤±¤òÌÜÏÀ¤ó¤À¤â¤Î¤Ç¤¹¡£²æ¡¹¥³¥ß¥å¥Ë¥Æ
-¥£¤ÎÃæ¤Ç¤Ï¥¢¥Ã¥×¥°¥ì¡¼¥É¤·¤Ê¤¤¤Û¤¦¤¬¤â¤Ã¤È¥ê¥¹¥¯¤¬¹â¤¤¤â¤Î¤È¹Í¤¨¤é¤ì¤Æ¤¤¤Þ¤¹¡£
+PostgreSQL¤Î¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¤ÏÄ̾¥·¥¹¥Æ¥à¥Æ¡¼¥Ö¥ë¤È¥Ç¡¼¥¿¤ÎÆâÉô¥Õ¥©¡¼¥Þ¥Ã¥È
+¤òÊѹ¹¤·¤Þ¤¹¡£¤³¤ì¤é¤ÎÊѹ¹¤Ï¤¿¤¤¤Æ¤¤¤ÏÊ£»¨¤Ê¤Î¤Ç¤Ç¡¢¥Ç¡¼¥¿¥Õ¥¡¥¤¥ë¤Î¸åÊý¸ß´¹À
+¤ò°Ý»ý¤·¤¿¤ê¤Ï¤·¤Þ¤»¤ó¡£¥á¥¸¥ã¡¼¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¤¿¤á¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥À¥ó¥×/
+¥ê¥í¡¼¥É¤¬É¬Íפˤʤê¤Þ¤¹¡£
-¤·¤«¤·¡¢¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¡Ê¤¿¤È¤¨¤Ð¡¢7.3 ¤«¤é 7.4 ¤Î¤è¤¦¤Ê¡Ë¤Ç¤Ï¡¢¥·¥¹¥Æ¥à¥Æ¡¼¥Ö
-¥ë¤ä¥Ç¡¼¥¿¥Õ¥¡¥¤¥ë¤ÎÆâÉô¥Õ¥©¡¼¥Þ¥Ã¥È¤ÎÊѹ¹¤ò¤·¤Ð¤·¤Ð¹Ô¤Ê¤¤¤Þ¤¹¡£¤³¤ì¤é¤ÎÊѹ¹¤Ï
-¤¿¤¤¤Æ¤¤Ê£»¨¤Ç¡¢¤½¤Î¤¿¤á²æ¡¹¤Ï¥Ç¡¼¥¿¥Õ¥¡¥¤¥ë¤Î¤¿¤á¤Î¸åÊý¸ß´¹À¤ò°Ý»ý¤¹¤ë¤³¤È¤¬
-¤Ç¤¤Þ¤»¤ó¡£¥á¥¸¥ã¡¼¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¤¿¤á¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥À¥ó¥×/¥ê¥í¡¼¥É¤¬É¬
-ÍפǤ¹¡£
+¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Ï¡¢¤¿¤È¤¨¤Ð¡¢8.1.5 ¤«¤é8.1.6¤Ø¤Î¤è¤¦¤Ë¡¢¥Ð¡¼¥¸¥ç¥óÈÖ¹æ¤Î3ÈÖÌÜ
+¤ÎÃͤòÁý¤ä¤·¤Þ¤¹¡£PostgreSQL¥Á¡¼¥à¤Ï¡¢¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤ËÂФ·¤Æ¤Ï¡¢¥Ð¥°¥Õ¥£¥¯¥¹
+¤·¤«¹Ô¤Ê¤¤¤Þ¤»¤ó¡£¤¹¤Ù¤Æ¤Î¥æ¡¼¥¶¤Ï¡¢¤Ç¤¤ë¤À¤±ºÇ¿·¤Î¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Ë¹¹¿·¤¹¤Ù
+¤¤Ç¤¹¡£¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ë¤Ï¡¢¾ï¤Ë¥ê¥¹¥¯¤¬¤Ä¤¤â¤Î¤Ç¤¹¤«¤é¡¢PostgreSQL¤Î¥Þ¥¤¥Ê¡¼
+½¤Àµ¥ê¥ê¡¼¥¹¤Ç¤Ï¡¢ÉÑÈˤËȯÀ¸¤·¤¿¤ê¡¢¥»¥¥å¥ê¥Æ¥£¤Ë´Ø·¸¤·¤¿¤ê¡¢¥Ç¡¼¥¿¤¬¤Ä¤Ö¤ì¤ë
+¥Ð¥°¤À¤±¤ò½¤Àµ¤·¡¢¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¥ê¥¹¥¯¤òºÇ¾®¸Â¤Ë¤È¤É¤á¤Þ¤¹¡£²æ¡¹¤Î¥³¥ß¥å¥Ë¥Æ
+¥£¤Ç¤Ï¡¢¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë¥ê¥¹¥¯¤è¤ê¤â¡¢¥¢¥Ã¥×¥°¥ì¡¼¥É¤·¤Ê¤¤¥ê¥¹¥¯¤Î¤Û¤¦¤¬¹â¤¤
+¤È¹Í¤¨¤Æ¤¤¤Þ¤¹¡£
-3.7) ¥Ï¡¼¥É¥¦¥§¥¢¤Ë¤Ï¤É¤ó¤Ê¥³¥ó¥Ô¥å¡¼¥¿¤ò»È¤¨¤Ð¤è¤¤¤Ç¤¹¤«¡©
+¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ë¤Ï¥À¥ó¥×¤È¥ê¥¹¥È¥¢¤ÎɬÍפϤʤ¯¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹
+¥µ¡¼¥Ð¤òÄä»ß¤·¤Æ¡¢¥¢¥Ã¥×¥Ç¡¼¥È¤µ¤ì¤¿¥Ð¥¤¥Ê¥ê¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¡¢¥µ¡¼¥Ð¤ò¥ê¥¹¥¿¡¼
+¥È¤·¤Þ¤¹¡£
+
+3.7) ¥Ï¡¼¥É¥¦¥§¥¢¤Ë¤Ï¤É¤Î¤è¤¦¤Ê¥³¥ó¥Ô¥å¡¼¥¿¤ò»È¤¨¤Ð¤è¤¤¤Ç¤¹¤«¡©
PC¥Ï¡¼¥É¥¦¥§¥¢¤Ï¤Û¤È¤ó¤É¸ß´¹À¤¬¤¢¤ê¤Þ¤¹¤Î¤Ç¡¢¤Û¤È¤ó¤É¤Î¿Í¤Ï¡¢¤¹¤Ù¤Æ¤ÎPC¥Ï¡¼¥É
¥¦¥§¥¢¤¬Æ±¤¸ÉʼÁ¤À¤È»×¤¤¹þ¤à·¹¸þ¤¬¤¢¤ê¤Þ¤¹¡£¤·¤«¤·¡¢¤½¤ì¤Ï´Ö°ã¤¤¤Ç¤¹¡£ECC RAM¡¢
ÎãÂê¤È¤·¤Æ¡¢³Æ¹Ô¤ËÀ°¿ô¤È¥Æ¥¥¹¥Èµ½Ò¤ò»ý¤Ä 100,000¹Ô¤Î¥Õ¥¡¥¤¥ë¤ò¹Í¤¨¤Æ¤ß¤Þ¤·¤ç
¤¦¡£¥Æ¥¥¹¥È¤Îʸ»úÎó¤ÎÊ¿¶ÑŤµ¤ò20¥Ð¥¤¥È¤È²¾Äꤹ¤ë¤È¡¢¥Õ¥é¥Ã¥È¥Õ¥¡¥¤¥ë¤ÎÂ礤µ
¤ÏÌó2.8MB ¤Ç¤¹¡£¤³¤Î¥Ç¡¼¥¿¤ò´Þ¤à PostgreSQL ¥Ç¡¼¥¿¥Ù¡¼¥¹¥Õ¥¡¥¤¥ë¤ÎÂ礤µ¤Ï¼¡¤Î
-¤è¤¦¤ËÌó5.6MB¤È¸«ÀѤâ¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡§
+¤è¤¦¤ËÌó5.2MB¤È¸«ÀѤâ¤ë¤³¤È¤¬¤Ç¤¤Þ¤¹¡§
- 28 bytes: ³Æ¥í¥¦¤Î¥Ø¥Ã¥À(³µ»»)
+ 24 bytes: ³Æ¥í¥¦¤Î¥Ø¥Ã¥À(³µ»»)
24 bytes: À°¿ô(int)¥Õ¥£¡¼¥ë¥É¤È¥Æ¥¥¹¥È(text)¥Õ¥£¡¼¥ë¥É
+ 4 bytes: ¥Ú¡¼¥¸¾å¤Î¥¿¥Ã¥×¥ë¤Ø¤Î¥Ý¥¤¥ó¥¿
----------------------------------------
- 56 bytes per row
+ 52 bytes per row
PostgreSQL ¤Î¥Ç¡¼¥¿¥Ú¡¼¥¸¥µ¥¤¥º¤Ï 8192¥Ð¥¤¥È(8KB)¤Ê¤Î¤Ç:
8192 bytes per page
------------------- = 146 rows per database page (ÀÚ¤ê¼Î¤Æ)
- 56 bytes per row
+ 52 bytes per row
100000 data rows
- -------------------- = 685 database pages (ÀÚ¤ê¾å¤²)
- 146 rows per page
+ -------------------- = 633 database pages (ÀÚ¤ê¾å¤²)
+ 158 rows per page
- 685 database pages * 8192 bytes per page = 5,611,520 bytes (5.6 MB)
+ 633 database pages * 8192 bytes per page = 5,185,536 bytes (5.2 MB)
¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¡¢¤³¤ì¤Û¤É¤Î¥ª¡¼¥Ð¥Ø¥Ã¥É¤ÏÍ׵ᤷ¤Þ¤»¤ó¤¬¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹ÉÕ¤±¤µ¤ì¤ë
¥Ç¡¼¥¿¤ò´Þ¤à°Ê¾å¡¢¤½¤ì¤Ê¤ê¤ËÂ礤¯¤Ê¤ê¤Þ¤¹¡£
4.18) ´Ø¿ô¤«¤éÊ£¿ô¤Î¥í¥¦¤Þ¤¿¤Ï¥«¥é¥à¤òÊÖ¤¹¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©
-½¸¹ç¤òÊÖ¤¹´Ø¿ô(Set Returning Functions): http://techdocs.postgresql.org/guides/
-SetReturningFunctions ¤ò»È¤¦¤È´Êñ¤Ç¤¹
+½¸¹ç¤òÊÖ¤¹´Ø¿ô(Set Returning Functions): http://www.postgresql.org/docs/
+techdocs.17
+
+¤ò»È¤¦¤È´Êñ¤Ç¤¹
¡£
[ÌõÃí¡§
ÆüËܸìÈǤÎÀ½ºî¤Ë¤Ä¤¤¤Æ¤Ï°Ê²¼¤ÎÄ̤ê¤Ç¤¹¡£
- ºÇ½ª¹¹¿·Æü: 2006ǯ12·î25Æü
+ ºÇ½ª¹¹¿·Æü: 2007ǯ03·î25Æü
ËÝÌõ¼Ô: ·¬Â¼ ½á (Jun Kuwamura <juk at PostgreSQL.jp>)
¤³¤ÎFAQ¤ÎÏÂÌõ¤ÎºîÀ®¤Ë¤¢¤¿¤ê¶¨ÎϤò¤·¤Æ¤¯¤À¤µ¤Ã¤¿Êý¡¹(·É¾Î¤Ïά¤µ¤»¤Æ¤¤¤¿¤À¤¤Þ¤¹):
Operating System (example: Linux 2.4.18) :
- PostgreSQL version (example: PostgreSQL 8.2.3): PostgreSQL 8.2.3
+ PostgreSQL version (example: PostgreSQL 8.2.4): PostgreSQL 8.2.4
Compiler used (example: gcc 3.3.5) :
alink="#0000ff">
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
- <P>Last updated: Tue Feb 6 22:16:17 EST 2007</P>
+ <P>Last updated: Wed Apr 18 23:05:05 EDT 2007</P>
<P>Current maintainer: Bruce Momjian (<A href=
"mailto:bruce@momjian.us">bruce@momjian.us</A>)
<H3 id="item1.6">1.6) What is the most recent release?</H3>
- <P>The latest release of PostgreSQL is version 8.2.3.</P>
+ <P>The latest release of PostgreSQL is version 8.2.4.</P>
<P>We plan to have a major release every year, with minor releases
every few months.</P>
<H3 id="item3.6">3.6) What is the upgrade process for PostgreSQL?</H3>
- <P>The PostgreSQL team makes only bug fixes in minor releases,
- so, for example, upgrading from 7.4.8 to 7.4.9 does not require
- a dump and restore; merely stop the database server, install
- the updated binaries, and restart the server.</P>
-
- <P>All users should upgrade to the most recent minor release as
- soon as it is available. While every upgrade has some risk,
- PostgreSQL minor releases are designed to fix only common bugs
- with the least risk. The community considers <i>not</i> upgrading
- more risky that upgrading.</P>
-
- <P>Major releases (e.g. from 7.3 to 7.4) often change the internal
- format of system tables and data files. These changes are often complex,
- so we don't maintain backward compatibility for data files. A dump/reload
- of the database is required for major upgrades.</P>
+ <P>See <a
+ href="http://www.postgresql.org/support/versioning">http://www.postgresql.org/support/versioning</a>.
+ </P>
<H3 id="item3.7">3.7) What computer hardware should I use?</H3>
but if reliability and performance are important it is wise to
research your hardware options thoroughly. Our email lists can be used
to discuss hardware options and tradeoffs.</P>
-
+
<HR>
<H2 align="center">Operational Questions</H2>
and text description on each line. Suppose the text string
avergages twenty bytes in length. The flat file would be 2.8 MB.
The size of the PostgreSQL database file containing this data can
- be estimated as 5.6 MB:</P>
+ be estimated as 5.2 MB:</P>
<PRE>
- 28 bytes: each row header (approximate)
+ 24 bytes: each row header (approximate)
24 bytes: one int field and one text field
+ 4 bytes: pointer on page to tuple
----------------------------------------
- 56 bytes per row
+ 52 bytes per row
The data page size in PostgreSQL is 8192 bytes (8 KB), so:
8192 bytes per page
- ------------------- = 146 rows per database page (rounded down)
- 56 bytes per row
+ ------------------- = 158 rows per database page (rounded down)
+ 52 bytes per row
100000 data rows
- -------------------- = 685 database pages (rounded up)
- 146 rows per page
+ -------------------- = 633 database pages (rounded up)
+ 158 rows per page
-685 database pages * 8192 bytes per page = 5,611,520 bytes (5.6 MB)
+633 database pages * 8192 bytes per page = 5,185,536 bytes (5.2 MB)
</PRE>
<P>Indexes do not require as much overhead, but do contain the data
columns from a function?</H3>
<P>It is easy using set-returning functions,
- <a href="http://techdocs.postgresql.org/guides/SetReturningFunctions">
- http://techdocs.postgresql.org/guides/SetReturningFunctions</a></P>.
+ <a href="http://www.postgresql.org/docs/techdocs.17">
+ http://www.postgresql.org/docs/techdocs.17</a></P>.
<H3 id="item4.19">4.19) Why do I get "relation with OID #####
does not exist" errors when accessing temporary tables in PL/PgSQL
<H1>Developer's Frequently Asked Questions (FAQ) for
PostgreSQL</H1>
- <P>Last updated: Thu Jan 4 16:00:00 EST 2007</P>
+ <P>Last updated: Mon Mar 19 12:52:30 EDT 2007</P>
<P>Current maintainer: Bruce Momjian (<A href=
"mailto:bruce@momjian.us">bruce@momjian.us</A>)<BR>
assistance?<BR>
<A href="#item1.18">1.18</A>) How do I get involved in PostgreSQL web
site development?<BR>
- <A href="#item1.19">1.19</A>) What is the timeline for the next major
- PostgreSQL release?<BR>
+ <A href="#item1.19">1.19</A>) Why haven't you replaced CVS with SVN, Git,
+ Monotone, VSS, <insert your favorite SCM system here>?
<H2>Technical Questions</H2>
<P>Some developers use compilers from other software vendors with
mixed results.</P>
- <P>Developers who are regularly rebuilding the source often pass
- the --enable-depend flag to <I>configure</I>. The result is that
- when you make a modification to a C header file, all files depend
- upon that file are also rebuilt.</P>
+ <P>Developers who regularly rebuild the source often pass the
+ --enable-depend flag to <I>configure</I>. The result is that when you
+ make a modification to a C header file, all files depend upon that
+ file are also rebuilt.</P>
+
+ <P><I>src/Makefile.custom</I> can be used to set environment variables,
+ like <I>CUSTOM_COPT</I>, that are used for every compile.
<H3 id="item1.3">1.3) What areas need work?</H3>
Outstanding features are detailed in the TODO list. This is located
preferable if the file changes are single-line changes and do not
rely on surrounding lines.)</li>
- <li>PostgreSQL is licensed under a BSD license, so any submissions must
- conform to the BSD license to be included. If you use code that is
- available under some other license that is BSD compatible (eg. public
- domain) please note that code in your email submission</li>
+ <li>PostgreSQL is licensed under a BSD license. By posting a patch
+ to the public PostgreSQL mailling lists, you are giving the PostgreSQL
+ Global Development Group the non-revokable right to distribute your
+ patch under the BSD license.</li>
<li>Confirm that your changes can pass the regression tests. If your
changes are port specific, please list the ports you have tested it
on.</li>
- <li>Provide an implementation overview, preferably in code comments.
- Following the surrounding code commenting style is usually a good
- approach.</li>
+ <li>If you are adding a new feature, confirm that it has been tested
+ thoroughly. Try to test the feature in all conceivable
+ scenarios.</li>
<li>New feature patches should also be accompanied by documentation
patches. If you need help checking the SQL standard, see <a href=
"#item1.16">1.16</a>.</li>
- <li>If you are adding a new feature, confirm that it has been tested
- thoroughly. Try to test the feature in all conceivable
- scenarios.</li>
+ <li>Provide an implementation overview, preferably in code comments.
+ Following the surrounding code commenting style is usually a good
+ approach.</li>
<li>If it is a performance patch, please provide confirming test
results to show the benefit of your patch. It is OK to post patches
the source code is available at <A href=
"http://gborg.postgresql.org/project/pgweb/projdisplay.php">http://gborg.postgresql.org/project/pgweb/projdisplay.php</A>
, the code for the next version of the website is under the
- "portal" module.
+ "portal" module.</P>
+
+ <H3 id="item1.19">1.19) Why haven't you replaced CVS with SVN, Git,
+ Monotone, VSS, <insert your favorite SCMS here>?</H3>
+
+ <P>Currently the core developers see no SCMS that will provide
+ enough benefit to outwiegh the pain involved in moving to a new
+ SCMS. Typical problems that must be addressed by any new SCMS include:</P>
+
+ <ul>
+ <li>Run natively on all of our <a href="http://www.postgresql.org/docs/current/interactive/supported-platforms.html">supported platforms</a>.</li>
+ <li>Integrate into the <a href="http://pgbuildfarm.org/">Buildfarm</a>.</li>
+ <li>Import our entire CVS Repository while preserving complete history.</li>
+ <li>Allow for anonymous checkouts.</li>
+ </ul>
+
+ <P>Currently there is no intention for switching to a new SCMS until at least the
+ end of the 8.4 development cycle sometime in late 2008. For more information
+ please refer to the mailing list archives.</P>
+
<H2>Technical Questions</H2>
requires a compile with <I>-DLINUX_PROFILE</I> for proper
profiling.</P>
- <H3 id="item2.9">2.9) What is the timeline for the next major
- PostgreSQL release?<BR>
-
- <P>The development schedule for the 8.3 release is:</P>
- <DL>
- <DD>March 1, 2007</DD>
- <DT>Initial community review of all major feature patches</DT>
- <DD>April 1, 2007</DD>
- <DT>Feature freeze, all patches must be submitted for review and application</DT>
- <DD>mid-May, 2007</DD>
- <DT>All patches applied, beta testing begins</DT>
- <DD>July, 2007</DD>
- <DT>Release of 8.3.0</DT>
- </DL>
-
- <P>Patches that appear after appropriate dates are typically
- not applied but held for the next major release.</P>
-
</BODY>
</HTML>
<h1 style="text-align: center;">Compiling PostgreSQL On Native Win32 FAQ<br>
</h1>
<P>Last updated: Thu Oct 14 18:22:57 EDT 2004</P>
-<P>Current maintainer: Bruce Momjian
(<A href=
-"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
+<P>Current maintainer: Bruce Momjian
<<A href=
+"mailto:bruce@momjian.us">bruce@momjian.us</A>><BR>
</P>
<P>The most recent version of this document can be viewed at <A href=
"http://www.postgresql.org/docs/faqs.FAQ_MINGW.html">
http://www.postgresql.org/docs/faqs.FAQ_MINGW.html</A>.</P>
-<P>The FAQ
for running PostgreSQL on native Win32 is at <A href=
-"http://pginstaller.projects.postgresql.org/FAQ_windows.html">
-http://pginstaller.projects.postgresql.org/FAQ_windows.html</A>.</P>
+<P>The FAQ
Running & Installing PostgreSQL On Native Windows is at <A href=
+"http://pginstaller.projects.postgresql.org/faq/FAQ_windows.html">
+http://pginstaller.projects.postgresql.org/faq/FAQ_windows.html</A>.</P>
<p>The native Win32 port is built from source using MinGW tools.
There is also a precompiled binary installer called <span
style="font-style: italic;">pginstaller</span> which you can find at
from <a href="http://pgfoundry.org/projects/pginstaller">http://pgfoundry.org/projects/pginstaller</a>.
It is a fully native build and uses no additional software like MinGW.
-The ready-made instlaler files are available on the main PostgreSQL ftp servers
+The ready-made installer files are available on the main PostgreSQL ftp servers
in the binary/win32 directory.
<br>
</p>
<h4><a name="1.13">1.13</a>) Wie sende ich einen Fehlerbericht?</h4>
- <p>Bitte besuchen Sie die PostgreSQL-BugTool-Seite <a href="http://www.postgresql.org/bugform.html">http://www.postgresql.org/bugform.html</a>,
+ <p>Bitte besuchen Sie die PostgreSQL-BugTool-Seite <a href="http://www.postgresql.org/support/submitbug">http://www.postgresql.org/support/submitbug</a>,
die Hinweise und Anleitungen zur Einreichung von Fehlerberichten enthält.</p>
<p>Überprüfe auch den ftp-Server <a href="ftp://ftp.postgresql.org/pub/">ftp://ftp.postgresql.org/pub/</a>,
<TITLE>PostgreSQL FAQ in Japanese</TITLE>
</HEAD>
<BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#FF0000" VLINK="#A00000" ALINK="#0000FF">
-<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=x-euc-jp">
+<META http-equiv="Content-Type" content="text/html; charset=EUC-JP">
<div id="pgContentWrap">
<h1>PostgreSQL(¥Ý¥¹¥È¥°¥ì¥¹¡¦¥¥å¡¼¡¦¥¨¥ë)¤Ë¤Ä¤¤¤Æ¤è¤¯¤¢¤ë¼ÁÌä¤È¤½¤Î²òÅú(FAQ)</h1>
-<p>¸¶Ê¸ºÇ½ª¹¹¿·Æü: Mon Dec 11 17:45:54 EST 2006</p>
+<p>¸¶Ê¸ºÇ½ª¹¹¿·Æü: Tue Mar 20 13:43:40 EDT 2007</p>
<p>¸½ºß¤Î°Ý»ý´ÉÍý¼Ô: Bruce Momjian (<A
href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br />
Maintainer of Japanese Translation: Jun Kuwamura (<A
<a href="#item1.11">1.11</a>) <small>SQL</small>¤Ï¤É¤¦¤¹¤ì¤Ð³Ø¤Ù¤Þ¤¹¤«¡©<br />
<a href="#item1.12">1.12</a>) ¥Ñ¥Ã¥Á¤òÄ󶡤·¤¿¤ê¡¢³«È¯¥Á¡¼¥à»²²Ã¤¹¤ë¤Ë¤Ï¤É¤¦¤¹¤ì¤Ð¤è¤¤¤Ç¤¹¤«¡©<br />
<a href="#item1.13">1.13</a>) ¾¤Î<small>DBMS</small>¤ÈÈæ¤Ù¤ÆPostgreSQL¤Ï¤É¤¦¤Ê¤Î¤Ç¤¹¤«¡©<br />
-
+<a href="#item1.14">1.14</a>) PostgreSQL¤Ï¹ñËè¤ÎºÇ¿·¤Î²Æ»þ´Ö¤ÎÊѹ¹¤ò°·¤¤¤Þ¤¹¤«¡©<br />
<h2 align="center">¥æ¡¼¥¶¡¦¥¯¥é¥¤¥¢¥ó¥È¤Î¼ÁÌä</h2>
<a href="#item3.3">3.3</a>) ¤è¤êÎɤ¤Àǽ¤òÆÀ¤ë¤¿¤á¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¡¦¥¨¥ó¥¸¥ó¤ò¤É¤Î¤è¤¦¤ËÄ´À°¤·¤Þ¤¹¤«¡©<br />
<a href="#item3.4">3.4</a>) ¤É¤Î¤è¤¦¤Ê¥Ç¥Ð¥°µ¡Ç½¤¬»È¤¨¤Þ¤¹¤«¡©<br />
<a href="#item3.5">3.5</a>) Àܳ¤·¤è¤¦¤È¤¹¤ë¤È¤¤Ë <i>'Sorry, too many clients'</i> ¤¬½Ð¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©<br />
-<a href="#item3.6">3.6</a>) PostgreSQL¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¼ê½ç¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©<br />
-<a href="#item3.7">3.7</a>) ¥Ï¡¼¥É¥¦¥§¥¢¤Ë¤Ï¤É¤ó¤Ê¥³¥ó¥Ô¥å¡¼¥¿¤ò»È¤¨¤Ð¤è¤¤¤Ç¤¹¤«¡©<br />
+<a href="#item3.6">3.6</a>) PostgreSQL¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¼ê½ç¤Ï¤É¤¦¤Ê¤ê¤Þ¤¹¤«¡©<br />
+<a href="#item3.7">3.7</a>) ¥Ï¡¼¥É¥¦¥§¥¢¤Ë¤Ï¤É¤Τ褦¤Ê¥³¥ó¥Ô¥å¡¼¥¿¤ò»È¤¨¤Ð¤è¤¤¤Ç¤¹¤«¡©<br />
<h2 align="center">Áàºî¾å¤Î¼ÁÌä</h2>
<a href="#item4.1">4.1</a>) ºÇ½é¤Î¤¤¤¯¤Ä¤«¤Î¥í¥¦¤Î¤ß¤ò <small>select</small> ¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡© ¥é¥ó¥À¥à¤Ê¥í¥¦¡© <br />
-<a href="#item4.7">4.2</a>) ÄêµÁ¤µ¤ì¤¿¥Æ¡¼¥Ö¥ë¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¡¢¤ª¤è¤Ó¡¢¥æ¡¼¥¶¤ò¤É¤Î¤è¤¦¤Ë¤·¤Æ¸«¤Ä¤±½Ð¤·¤Þ¤¹¤«¡©<br />
+<a href="#item4.2">4.2</a>) ÄêµÁ¤µ¤ì¤¿¥Æ¡¼¥Ö¥ë¡¢¥¤¥ó¥Ç¥Ã¥¯¥¹¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¡¢¤ª¤è¤Ó¡¢¥æ¡¼¥¶¤ò¤É¤Î¤è¤¦¤Ë¤·¤Æ¸«¤Ä¤±½Ð¤·¤Þ¤¹¤«¡©<br />
<a href="#item4.3">4.3</a>) ¥«¥é¥à¤Î¥Ç¡¼¥¿¥¿¥¤¥×¤òÊѹ¹¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©<br />
<a href="#item4.4">4.4</a>) ¥í¥¦¡¢¥Æ¡¼¥Ö¥ë¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤ÎºÇÂ祵¥¤¥º¤Ï¡©<br />
<a href="#item4.5">4.5</a>) °ìÈÌŪ¤Ê¥Æ¥¥¹¥È¥Õ¥¡¥¤¥ë¤Î¥Ç¡¼¥¿¤òÊݸ¤¹¤ë¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥Ç¥£¥¹¥¯ÍÆÎ̤ϤɤΤ¯¤é¤¤É¬ÍפǤ¹¤«¡©<br />
<small><pre>
POSTGRESQL ¥Ç¡¼¥¿¥Ù¡¼¥¹´ÉÍý¥·¥¹¥Æ¥à
- ÉôʬŪÃøºî¸¢ (c) 1996-2006, PostgreSQL¹ñºÝ³«È¯¥Á¡¼¥à
+ ÉôʬŪÃøºî¸¢ (c) 1996-2007, PostgreSQL¹ñºÝ³«È¯¥Á¡¼¥à
ÉôʬŪÃøºî¸¢ (c) 1994-1996 ¥«¥ê¥Õ¥©¥ë¥Ë¥¢Âç³ØËܹ»
<h4 id="item1.6">1.6</a>) ºÇ¿·¤Î¥ê¥ê¡¼¥¹¤Ï¤É¤ì¤Ç¤¹¤«¡©</h4>
- <p>PostgreSQL ¤ÎºÇ¿·ÈǤϥС¼¥¸¥ç¥ó 8.2.0 ¤Ç¤¹¡£</p>
+ <p>PostgreSQL ¤ÎºÇ¿·ÈǤϥС¼¥¸¥ç¥ó 8.2.3 ¤Ç¤¹¡£</p>
<p>²æ¡¹¤Ï¡¢1ǯËè¤Ë¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¤ò¡¢¿ô¥õ·î¤´¤È¤Î¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤ò
¹Ô¤Ê¤¦¤³¤È¤ò·×²è¤·¤Æ¤¤¤Þ¤¹¡£</p>
</dl>
</p>
+<h3 id="item1.14">1.14) PostgreSQL¤Ï¹ñËè¤ÎºÇ¿·¤Î²Æ»þ´Ö¤ÎÊѹ¹¤ò°·¤¤¤Þ¤¹¤«¡©</h3>
+
+ <p>¹ç½£¹ñ¤Î²Æ»þ´Ö¤ÎÊѹ¹¤Ï¡¢PostgreSQL¤Î¥ê¥ê¡¼¥¹8.0.4°Ê¹ß[4+]¤È¡¢¤½¤Î
+ ¸å¤Î¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¡¢¤¿¤È¤¨¤Ð 8.1 ¤Ë¤Ï´Þ¤Þ¤ì¤Æ¤¤¤Þ¤¹¡£¥«¥Ê¥À¤È¥ª¡¼
+ À¾Éô¥¹¥È¥é¥ê¥¢¤ÎÊѹ¹¤Ï¡¢8.0.[10+], 8.1.[6+] ¤ª¤è¤Ó¡¢¤½¤Î¸å¤Î¥á¥¸¥ã¡¼
+ ¥ê¥ê¡¼¥¹¤Î¤¹¤Ù¤Æ¤Ë´Þ¤Þ¤ì¤Þ¤¹¡£8.0¤è¤êÁ°¤ÎPosrgreSQL¤Ç¤Ï¥ª¥Ú¥ì¡¼¥Æ¥£
+ ¥ó¥°¥·¥¹¥Æ¥à¤Î¥¿¥¤¥à¥¾¡¼¥ó¥Ç¡¼¥¿¥Ù¡¼¥¹¤ò²Æ»þ´Ö¾ðÊó¤Î¤¿¤á¤Ë»È¤Ã¤Æ¤¤
+ ¤Þ¤¹¡£</p>
+
<hr />
<h2 align="center">¥æ¡¼¥¶¡¦¥¯¥é¥¤¥¢¥ó¥È¤Î¼ÁÌä</h2>
<p>¥µ¡¼¥Ð¹½À®ÊÑ¿ô¤Ë¤Ï¿¤¯¤Î <code>log_*</code> ¤¬¤¢¤ê¡¢¥¯¥¨¥ê¤È¥×¥í
¥»¥¹¤ÎÅý·×¤ò½ÐÎϤ¹¤ë¤³¤È¤¬¤Ç¤¡¢¥Ç¥Ð¥°¤ÈÀǽ·×¬¤Ë¤È¤Æ¤âÊØÍø¤Ç¤¹¡£</p>
+
<h4 id="item3.5">3.5</a>) Àܳ¤·¤è¤¦¤È¤¹¤ë¤È¤¤Ë <i>'Sorry, too many clients'</i> ¤¬½Ð¤ë¤Î¤Ï¤Ê¤¼¤Ç¤¹¤«¡©</h4>
<p> ´ûÄê¤Ç¤ÎÀ©¸Â¤Ç¤¢¤ë 100 ¤Î¥Ç¡¼¥¿¥Ù¡¼¥¹¥»¥Ã¥·¥ç¥ó¤Ë㤷¤Æ¤·¤Þ¤Ã¤Æ
<i>max_connections</i> ¤ÎÃͤòÊѹ¹¤·¤Æ <i>postmaster</i>¤òºÆµ¯Æ°¤¹¤ë
¤³¤È¤Ç²Äǽ¤Ë¤Ê¤ê¤Þ¤¹¡£</p>
-<h4 id="item3.6">3.6</a>) PostgreSQL¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¼ê½ç¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©</h4>
- <p>PostgreSQL¥Á¡¼¥à¤Ï¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Ç¤Ï¥Ð¥°¤Î½¤Àµ¤·¤«¹Ô¤Ê¤¤¤Þ¤»¤ó
- ¤Î¤Ç¡¢¤¿¤È¤¨¤Ð 7.4.8 ¤«¤é 7.4.9 ¤Ø¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ë¥À¥ó¥×¤È¥ê¥¹¥È
- ¥¢¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£¤·¤¿¤¬¤Ã¤Æ¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¥µ¡¼¥Ð¤ò°ì»þŪ¤ËÄä»ß¤·¤Æ¡¢
- ¥¢¥Ã¥×¥Ç¡¼¥È¤·¤¿¥Ð¥¤¥Ê¥ê¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¡¢¤½¤·¤Æ¡¢¥µ¡¼¥Ð¤ò¥ê¥¹¥¿¡¼¥È
- ¤¹¤ë¤À¤±¤Ç¤¹¡£</p>
+<h4 id="item3.6">3.6</a>) PostgreSQL¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¼ê½ç¤Ï¤É¤¦¤Ê¤ê¤Þ¤¹¤«¡©</h4>
+
+ <p>¥Ð¡¼¥¸¥ç¥óÈÖ¹æÉÕ¤±¤ÎÊý¿Ë¤Ë¤Ä¤¤¤Æ¤Ï¡¢<a
+ href="http://www.postgresql.org/support/versioning">http://www.postgresql.org/support/versioning</a>
+ ¤ò¤´Í÷¤¯¤À¤µ¤¤¡£
+ </p>
+
+ <p>¿·¤·¤¤µ¡Ç½¤òÀ¹¤ê¹þ¤àPostgreSQL¤Î¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¤Ï¤À¤¤¤¿¤¤Ç¯¤Ë1²ó
+ ÄøÅٹԤʤ¤¤Þ¤¹¡£¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¤Ï¡¢¤¿¤È¤¨¤Ð¡¢8.1¤«¤é8.2¤Ø¤Î¤è¤¦¤Ë¡¢
+ ¥Ð¡¼¥¸¥ç¥óÈÖ¹æ¤Î1ÈÖÌܤ«2ÈÖÌܤÎÉôʬ¤òÁý¤ä¤·¤Æ¤æ¤¤Þ¤¹¡£</p>
+
+ <p>PostgreSQL¤Î¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¤ÏÄ̾¥·¥¹¥Æ¥à¥Æ¡¼¥Ö¥ë¤È¥Ç¡¼¥¿¤ÎÆâ
+ Éô¥Õ¥©¡¼¥Þ¥Ã¥È¤òÊѹ¹¤·¤Þ¤¹¡£¤³¤ì¤é¤ÎÊѹ¹¤Ï¤¿¤¤¤Æ¤¤¤ÏÊ£»¨¤Ê¤Î¤Ç¤Ç¡¢¥Ç¡¼
+ ¥¿¥Õ¥¡¥¤¥ë¤Î¸åÊý¸ß´¹À¤ò°Ý»ý¤·¤¿¤ê¤Ï¤·¤Þ¤»¤ó¡£¥á¥¸¥ã¡¼¥¢¥Ã¥×¥°¥ì¡¼¥É
+ ¤Î¤¿¤á¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥À¥ó¥×/¥ê¥í¡¼¥É¤¬É¬Íפˤʤê¤Þ¤¹¡£</p>
- <p>Á´¥æ¡¼¥¶¤Ï¤Ç¤¤ë¤À¤±Á᤯ºÇ¿·¤Î¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Ë¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹
- ¤ë¤Ù¤¤Ç¤¹¡£¤¹¤Ù¤Æ¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ë¥ê¥¹¥¯¤Ï¤Ä¤¤â¤Î¤Ç¤¹¤¬¡¢
- PostgreSQL¤Î¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Ï¡¢¤Ê¤ë¤Ù¤¯¾®¤µ¤Ê¥ê¥¹¥¯¤Ç°ìÈÌŪ¤Ê¥Ð¥°¤Î
- ½¤Àµ¤À¤±¤òÌÜÏÀ¤ó¤À¤â¤Î¤Ç¤¹¡£²æ¡¹¥³¥ß¥å¥Ë¥Æ¥£¤ÎÃæ¤Ç¤Ï¥¢¥Ã¥×¥°¥ì¡¼¥É
- <i>¤·¤Ê¤¤</i>¤Û¤¦¤¬¤â¤Ã¤È¥ê¥¹¥¯¤¬¹â¤¤¤â¤Î¤È¹Í¤¨¤é¤ì¤Æ¤¤¤Þ¤¹¡£</p>
+ <p>¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Ï¡¢¤¿¤È¤¨¤Ð¡¢8.1.5 ¤«¤é8.1.6¤Ø¤Î¤è¤¦¤Ë¡¢¥Ð¡¼¥¸¥ç
+ ¥óÈÖ¹æ¤Î3ÈÖÌܤÎÃͤòÁý¤ä¤·¤Þ¤¹¡£PostgreSQL¥Á¡¼¥à¤Ï¡¢¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹
+ ¤ËÂФ·¤Æ¤Ï¡¢¥Ð¥°¥Õ¥£¥¯¥¹¤·¤«¹Ô¤Ê¤¤¤Þ¤»¤ó¡£¤¹¤Ù¤Æ¤Î¥æ¡¼¥¶¤Ï¡¢¤Ç¤¤ë¤À
+ ¤±ºÇ¿·¤Î¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Ë¹¹¿·¤¹¤Ù¤¤Ç¤¹¡£¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ë¤Ï¡¢¾ï¤Ë¥ê
+ ¥¹¥¯¤¬¤Ä¤¤â¤Î¤Ç¤¹¤«¤é¡¢PostgreSQL¤Î¥Þ¥¤¥Ê¡¼½¤Àµ¥ê¥ê¡¼¥¹¤Ç¤Ï¡¢ÉÑÈˤË
+ ȯÀ¸¤·¤¿¤ê¡¢¥»¥¥å¥ê¥Æ¥£¤Ë´Ø·¸¤·¤¿¤ê¡¢¥Ç¡¼¥¿¤¬¤Ä¤Ö¤ì¤ë¥Ð¥°¤À¤±¤ò½¤Àµ
+ ¤·¡¢¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¥ê¥¹¥¯¤òºÇ¾®¸Â¤Ë¤È¤É¤á¤Þ¤¹¡£²æ¡¹¤Î¥³¥ß¥å¥Ë¥Æ¥£¤Ç
+ ¤Ï¡¢¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë¥ê¥¹¥¯¤è¤ê¤â¡¢¥¢¥Ã¥×¥°¥ì¡¼¥É<i>¤·¤Ê¤¤¥ê¥¹¥¯</i>
+ ¤Î¤Û¤¦¤¬¹â¤¤¤È¹Í¤¨¤Æ¤¤¤Þ¤¹¡£</p>
- <p>¤·¤«¤·¡¢¥á¥¸¥ã¡¼¥ê¥ê¡¼¥¹¡Ê¤¿¤È¤¨¤Ð¡¢7.3 ¤«¤é 7.4 ¤Î¤è¤¦¤Ê¡Ë¤Ç¤Ï¡¢
- ¥·¥¹¥Æ¥à¥Æ¡¼¥Ö¥ë¤ä¥Ç¡¼¥¿¥Õ¥¡¥¤¥ë¤ÎÆâÉô¥Õ¥©¡¼¥Þ¥Ã¥È¤ÎÊѹ¹¤ò¤·¤Ð¤·¤Ð¹Ô
- ¤Ê¤¤¤Þ¤¹¡£¤³¤ì¤é¤ÎÊѹ¹¤Ï¤¿¤¤¤Æ¤¤Ê£»¨¤Ç¡¢¤½¤Î¤¿¤á²æ¡¹¤Ï¥Ç¡¼¥¿¥Õ¥¡¥¤¥ë
- ¤Î¤¿¤á¤Î¸åÊý¸ß´¹À¤ò°Ý»ý¤¹¤ë¤³¤È¤¬¤Ç¤¤Þ¤»¤ó¡£¥á¥¸¥ã¡¼¥¢¥Ã¥×¥°¥ì¡¼¥É
- ¤Î¤¿¤á¤Ë¤Ï¡¢¥Ç¡¼¥¿¥Ù¡¼¥¹¤Î¥À¥ó¥×/¥ê¥í¡¼¥É¤¬É¬ÍפǤ¹¡£</p>
+ <p>¥Þ¥¤¥Ê¡¼¥ê¥ê¡¼¥¹¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ë¤Ï¥À¥ó¥×¤È¥ê¥¹¥È¥¢¤ÎɬÍפϤʤ¯¡¢
+ ¥Ç¡¼¥¿¥Ù¡¼¥¹¥µ¡¼¥Ð¤òÄä»ß¤·¤Æ¡¢¥¢¥Ã¥×¥Ç¡¼¥È¤µ¤ì¤¿¥Ð¥¤¥Ê¥ê¤ò¥¤¥ó¥¹¥È¡¼
+ ¥ë¤·¡¢¥µ¡¼¥Ð¤ò¥ê¥¹¥¿¡¼¥È¤·¤Þ¤¹¡£</p>
-<h4 id="item3.7">3.7</a>) ¥Ï¡¼¥É¥¦¥§¥¢¤Ë¤Ï¤É¤ó¤Ê¥³¥ó¥Ô¥å¡¼¥¿¤ò»È¤¨¤Ð¤è¤¤¤Ç¤¹¤«¡©</h4>
+
+<h4 id="item3.7">3.7</a>) ¥Ï¡¼¥É¥¦¥§¥¢¤Ë¤Ï¤É¤Î¤è¤¦¤Ê¥³¥ó¥Ô¥å¡¼¥¿¤ò»È¤¨¤Ð¤è¤¤¤Ç¤¹¤«¡©</h4>
<p>PC¥Ï¡¼¥É¥¦¥§¥¢¤Ï¤Û¤È¤ó¤É¸ß´¹À¤¬¤¢¤ê¤Þ¤¹¤Î¤Ç¡¢¤Û¤È¤ó¤É¤Î¿Í¤Ï¡¢¤¹
¤Ù¤Æ¤ÎPC¥Ï¡¼¥É¥¦¥§¥¢¤¬Æ±¤¸ÉʼÁ¤À¤È»×¤¤¹þ¤à·¹¸þ¤¬¤¢¤ê¤Þ¤¹¡£¤·¤«¤·¡¢¤½
<hr />
+
<h2 align="center">Áàºî¾å¤Î¼ÁÌä</h2>
<h4 id="item4.1">4.1</a>) ºÇ½é¤Î¿ô¥í¥¦¤Î¤ß¤ò <small>SELECT</small>¤¹¤ë¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©¥é¥ó¥À¥à¤Ê¥í¥¦¡©
<p> ÎãÂê¤È¤·¤Æ¡¢³Æ¹Ô¤ËÀ°¿ô¤È¥Æ¥¥¹¥Èµ½Ò¤ò»ý¤Ä 100,000¹Ô¤Î¥Õ¥¡¥¤¥ë¤ò
¹Í¤¨¤Æ¤ß¤Þ¤·¤ç¤¦¡£¥Æ¥¥¹¥È¤Îʸ»úÎó¤ÎÊ¿¶ÑŤµ¤ò20¥Ð¥¤¥È¤È²¾Äꤹ¤ë¤È¡¢
¥Õ¥é¥Ã¥È¥Õ¥¡¥¤¥ë¤ÎÂ礤µ¤ÏÌó2.8MB ¤Ç¤¹¡£¤³¤Î¥Ç¡¼¥¿¤ò´Þ¤à PostgreSQL
- ¥Ç¡¼¥¿¥Ù¡¼¥¹¥Õ¥¡¥¤¥ë¤ÎÂ礤µ¤Ï¼¡¤Î¤è¤¦¤ËÌó5.6MB¤È¸«ÀѤâ¤ë¤³¤È¤¬¤Ç¤
+ ¥Ç¡¼¥¿¥Ù¡¼¥¹¥Õ¥¡¥¤¥ë¤ÎÂ礤µ¤Ï¼¡¤Î¤è¤¦¤ËÌó5.2MB¤È¸«ÀѤâ¤ë¤³¤È¤¬¤Ç¤
¤Þ¤¹¡§
<pre>
- 28 bytes: ³Æ¥í¥¦¤Î¥Ø¥Ã¥À(³µ»»)
+ 24 bytes: ³Æ¥í¥¦¤Î¥Ø¥Ã¥À(³µ»»)
24 bytes: À°¿ô(int)¥Õ¥£¡¼¥ë¥É¤È¥Æ¥¥¹¥È(text)¥Õ¥£¡¼¥ë¥É
+ 4 bytes: ¥Ú¡¼¥¸¾å¤Î¥¿¥Ã¥×¥ë¤Ø¤Î¥Ý¥¤¥ó¥¿
----------------------------------------
- 56 bytes per row
+ 52 bytes per row
PostgreSQL ¤Î¥Ç¡¼¥¿¥Ú¡¼¥¸¥µ¥¤¥º¤Ï 8192¥Ð¥¤¥È(8KB)¤Ê¤Î¤Ç:
8192 bytes per page
------------------- = 146 rows per database page (ÀÚ¤ê¼Î¤Æ)
- 56 bytes per row
+ 52 bytes per row
100000 data rows
- -------------------- = 685 database pages (ÀÚ¤ê¾å¤²)
- 146 rows per page
+ -------------------- = 633 database pages (ÀÚ¤ê¾å¤²)
+ 158 rows per page
- 685 database pages * 8192 bytes per page = 5,611,520 bytes (5.6 MB)
+ 633 database pages * 8192 bytes per page = 5,185,536 bytes (5.2 MB)
</pre>
<p>¥¤¥ó¥Ç¥Ã¥¯¥¹¤Ï¡¢¤³¤ì¤Û¤É¤Î¥ª¡¼¥Ð¥Ø¥Ã¥É¤ÏÍ׵ᤷ¤Þ¤»¤ó¤¬¡¢¥¤¥ó¥Ç¥Ã
<h4 id="item4.18">4.18</a>) ´Ø¿ô¤«¤éÊ£¿ô¤Î¥í¥¦¤Þ¤¿¤Ï¥«¥é¥à¤òÊÖ¤¹¤Ë¤Ï¤É¤¦¤·¤Þ¤¹¤«¡©</h4>
<p>½¸¹ç¤òÊÖ¤¹´Ø¿ô(Set Returning Functions):
- <a href="http://techdocs.postgresql.org/guides/SetReturningFunctions">
- http://techdocs.postgresql.org/guides/SetReturningFunctions</a>
+ <a href="http://www.postgresql.org/docs/techdocs.17">
+ http://www.postgresql.org/docs/techdocs.17</a></p>
¤ò»È¤¦¤È´Êñ¤Ç¤¹</p>¡£
[ÌõÃí¡§
ÆüËܸìÈǤÎÀ½ºî¤Ë¤Ä¤¤¤Æ¤Ï°Ê²¼¤ÎÄ̤ê¤Ç¤¹¡£
- ºÇ½ª¹¹¿·Æü: 2006ǯ12·î25Æü
+ ºÇ½ª¹¹¿·Æü: 2007ǯ03·î25Æü
ËÝÌõ¼Ô: ·¬Â¼ ½á (<a href="mailto:juk at PostgreSQL.jp">Jun Kuwamura <juk at PostgreSQL.jp></a>)
¤³¤ÎFAQ¤ÎÏÂÌõ¤ÎºîÀ®¤Ë¤¢¤¿¤ê¶¨ÎϤò¤·¤Æ¤¯¤À¤µ¤Ã¤¿Êý¡¹(·É¾Î¤Ïά¤µ¤»¤Æ¤¤¤¿¤À¤¤Þ¤¹):
#define PACKAGE_STRING "PostgreSQL 8.2.3"
/* Define to the version of this package. */
-#define PACKAGE_VERSION "8.2.3"
+#define PACKAGE_VERSION "8.2.4"
/* PostgreSQL version as a string */
-#define PG_VERSION "8.2.3"
+#define PG_VERSION "8.2.4"
/* PostgreSQL version as a number */
-#define PG_VERSION_NUM 80203
+#define PG_VERSION_NUM 80204
/* Define to the one symbol short name of this package. */
#define PACKAGE_TARNAME "postgresql"
#include <winver.h>
VS_VERSION_INFO VERSIONINFO
- FILEVERSION 8,2,3,0
- PRODUCTVERSION 8,2,3,0
+ FILEVERSION 8,2,4,0
+ PRODUCTVERSION 8,2,4,0
FILEFLAGSMASK 0x3fL
FILEFLAGS 0
FILEOS VOS__WINDOWS32
BEGIN
VALUE "CompanyName", "\0"
VALUE "FileDescription", "PostgreSQL Access Library\0"
- VALUE "FileVersion", "8.2.3\0"
+ VALUE "FileVersion", "8.2.4\0"
VALUE "InternalName", "libpq\0"
VALUE "LegalCopyright", "Copyright (C) 2005\0"
VALUE "LegalTrademarks", "\0"
VALUE "OriginalFilename", "libpq.dll\0"
VALUE "ProductName", "PostgreSQL\0"
- VALUE "ProductVersion", "8.2.3\0"
+ VALUE "ProductVersion", "8.2.4\0"
END
END
BLOCK "VarFileInfo"
#include "pg_config.h"
VS_VERSION_INFO VERSIONINFO
- FILEVERSION 8,2,3,0
- PRODUCTVERSION 8,2,3,0
+ FILEVERSION 8,2,4,0
+ PRODUCTVERSION 8,2,4,0
FILEFLAGSMASK 0x17L
FILEFLAGS 0x0L
FILEOS VOS_NT_WINDOWS32
projects / thirdparty / postgresql.git / commitdiff
