|
|
|
|
@ -10,7 +10,7 @@ |
|
|
|
|
alink="#0000ff"> |
|
|
|
|
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> |
|
|
|
|
|
|
|
|
|
<P>Last updated: Wed Oct 17 13:34:42 EDT 2007</P> |
|
|
|
|
<P>Last updated: Fri Oct 26 14:59:45 EDT 2007</P> |
|
|
|
|
|
|
|
|
|
<P>Current maintainer: Bruce Momjian (<A href= |
|
|
|
|
"mailto:bruce@momjian.us">bruce@momjian.us</A>) |
|
|
|
|
@ -157,7 +157,7 @@ |
|
|
|
|
the community of developers and users, which anyone can join. All |
|
|
|
|
you need to do is subscribe to the mailing lists and participate in the |
|
|
|
|
discussions. (See the <a href="http://www.postgresql.org/docs/faqs.FAQ_DEV.html"> |
|
|
|
|
Developer's FAQ</A> for information on how to get involved in Postgres |
|
|
|
|
Developer's FAQ</A> for information on how to get involved in PostgreSQL |
|
|
|
|
development.)</P> |
|
|
|
|
|
|
|
|
|
<H3 id="item1.3">1.3) What is the copyright of |
|
|
|
|
@ -205,7 +205,7 @@ |
|
|
|
|
systems like Win2000 SP4, WinXP, and Win2003. A prepackaged installer is |
|
|
|
|
available at <a href= "http://pgfoundry.org/projects/pginstaller"> |
|
|
|
|
http://pgfoundry.org/projects/pginstaller</a>. MSDOS-based versions |
|
|
|
|
of Windows (Win95, Win98, WinMe) can run Postgres using Cygwin.</P> |
|
|
|
|
of Windows (Win95, Win98, WinMe) can run PostgreSQL using Cygwin.</P> |
|
|
|
|
|
|
|
|
|
<p>There is also a Novell Netware 6 port at |
|
|
|
|
<a href="http://forge.novell.com">http://forge.novell.com</a>, |
|
|
|
|
@ -254,7 +254,7 @@ |
|
|
|
|
http://www.postgresql.org/support/submitbug</A>. |
|
|
|
|
Also check out our ftp site <A href= |
|
|
|
|
"ftp://ftp.postgresql.org/pub/">ftp://ftp.postgresql.org/pub/</A> to |
|
|
|
|
see if there is a more recent Postgres version.</P> |
|
|
|
|
see if there is a more recent PostgreSQL version.</P> |
|
|
|
|
|
|
|
|
|
<P>Bugs submitted using the bug form or posted to any PostgreSQL mailing |
|
|
|
|
list typically generates one of the following replies:</P> |
|
|
|
|
@ -317,7 +317,7 @@ |
|
|
|
|
list up-to-date. In practice, bugs don't last very long in the |
|
|
|
|
software, and bugs that affect a large number of users are fixed |
|
|
|
|
rapidly. The only place to find all changes, improvements, and |
|
|
|
|
fixes in a Postgres release is to read the |
|
|
|
|
fixes in a PostgreSQL release is to read the |
|
|
|
|
<a href="http://www.postgresql.org/developer/sourcecode/">CVS</a> |
|
|
|
|
log messages. Even the release notes do not list every change |
|
|
|
|
made to the software.</P> |
|
|
|
|
@ -708,7 +708,7 @@ table?</TD><TD>unlimited</TD></TR> |
|
|
|
|
<P>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 Postgres database file containing this data can |
|
|
|
|
The size of the PostgreSQL database file containing this data can |
|
|
|
|
be estimated as 5.2 MB:</P> |
|
|
|
|
<PRE> |
|
|
|
|
24 bytes: each row header (approximate) |
|
|
|
|
@ -717,7 +717,7 @@ table?</TD><TD>unlimited</TD></TR> |
|
|
|
|
---------------------------------------- |
|
|
|
|
52 bytes per row |
|
|
|
|
|
|
|
|
|
The data page size in Postgres is 8192 bytes (8 KB), so: |
|
|
|
|
The data page size in PostgreSQL is 8192 bytes (8 KB), so: |
|
|
|
|
|
|
|
|
|
8192 bytes per page |
|
|
|
|
------------------- = 158 rows per database page (rounded down) |
|
|
|
|
|
Bruce Momjian
18 years ago