I am wondering if it is sane to mount PGDATA over NFS on many
machines and run posmaster backends on them, so that all the
postmasters are using the same database.
Obviously performance is going to suffer because network traffic
is going to be high, but later we may use a distributed filesystem
I understand that that WAL is an integral part of 7.1 and "disabling" is
not possible. I also don't want to switch back to 7.0 becuse I _DO_ need
the new features.
If I don't care for reliability (for reasons I outlined earlier in this
thread), are there other parameters I can set to optimize fo
On Mon, 30 Apr 2001, Oliver Vecernik wrote:
> Anuradha Ratnaweera wrote:
> >
> > Is there a way to disable write ahead logging (WAL) in 7.1?
>
> Why do you want to do this?
>
Because I have a copy of my real server on a laptop and I do all the
development on it. I
Is there a way to disable write ahead logging (WAL) in 7.1?
Thanks in advance.
Anuradha
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
I had to run a script which did few thousand queries on 7.1 few times and
after that even the queries that are done entirely based on indexes were
also _VERY_ slow. But I did a "vacuumdb dbname" as postgres user and after
that thigs were back to normal - very fast.
But I could _NOT_ reproduce th
Will vacuumdb help?
On Fri, 27 Apr 2001, Tom Lane wrote:
> Reiner Dassing <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> That shouldn't happen. Could we see the dump file? (Just the schema
> >> commands, not the data itself...)
>
> > Thank you for your help. Certainly I will give this
On Wed, 25 Apr 2001, Joel Burton wrote:
> Is there anything that datetime did that timestamp doesn't?
datetime is provided to ensure compatibility with older releases, although
they are not guranteed to exist in future releases (chapter 3.4 users
guide)
> Could you
>
>pg_dump | sed | ps
