scott.marlowe wrote:
> Also, running on SCSI drives will be much faster than running on IDE
> drives if the IDE drives have their caches disabled like they should,
> since they lie otherwise. Since SCSI disks don't usually lie, and are
> designed to handle multiple requests in parallel, they are m
On Sat, Feb 07, 2004 at 10:56:57AM -, Peter Galbavy wrote:
> Nice to see old fashioned misinformation being spread around the place...
Do you care to clarify that remark? Because there's _plenty_ of
evidence that some IDE drives do not tell the truth about what
they're doing, and that SCSI ha
Hi,
I compiled Postgressql 7.4.1 and installed it. Every thing was fine.
Starting the postmaster I got the message, that the port 5432 was already in
use and no IPV4 connection could be established. Well, the port is not in
use and with an other port number I got the same result. With the older
ve
Peter Georgi wrote:
> I compiled Postgressql 7.4.1 and installed it. Every thing was fine.
> Starting the postmaster I got the message, that the port 5432 was
> already in use and no IPV4 connection could be established. Well, the
> port is not in use and with an other port number I got the same
>
Hi,
We use postgresql for rather large databases. For a typical installation, a
pg_restore takes a couple of hours, at least (the dumpfiles are usually 2-4
gigabytes or so, including BLOBs). The machines are expected to be up 24/7,
so this dump/restore procedure makes upgrading unpopular. Is th
Palle Girgensohn <[EMAIL PROTECTED]> writes:
> The most obvious question is, can we use pg_upgrade from contrib? It seems
> not to have been updated since 7.3, and is generally documented as
> untested.
"Guaranteed not to work" is more like it. I have some ambitions of
rewriting it for future r
