On Mon, 2007-10-01 at 19:25 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
http://blogs.netapp.com/dave/2007/08/oracle-optimize.html
Not a whole lot of technical content there, but pretty interesting
nonetheless. I *think* that the issues we're seeing are largely in the
NFS
Alvaro Herrera wrote:
Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
http://blogs.netapp.com/dave/2007/08/oracle-optimize.html
Not a whole lot of technical content there, but pretty interesting
nonetheless. I *think* that the issues we're seeing are largely in the
NFS
Bruce Momjian wrote:
Alvaro Herrera wrote:
Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
http://blogs.netapp.com/dave/2007/08/oracle-optimize.html
Not a whole lot of technical content there, but pretty interesting
nonetheless. I *think* that the issues we're seeing are
On Mon, 2007-10-08 at 16:50 -0400, Alvaro Herrera wrote:
palloc uses malloc underneath. My thought is to replace that with
sbrk, mmap or something like that. Not very portable though, a lot of
work, and most likely not nearly enough benefits.
Yeah, I agree this isn't likely to be a win in
Tom,
Maybe we need to actively discourage people from running Postgres
against NFS-mounted data directories. Shane Kerr's paper cited above
mentions some other rather scary properties, including O_EXCL file
creation not really working properly.
Wouldn't you be describing a Linux-specific
Josh Berkus [EMAIL PROTECTED] writes:
Maybe we need to actively discourage people from running Postgres
against NFS-mounted data directories.
It's hard to reconcile this with the real-world performance of
PostgreSQL on NFS, which is happening all over the place. Most notably,
Joe Conway's
On Mon, 2007-10-01 at 10:13 -0700, Josh Berkus wrote:
Maybe we need to actively discourage people from running Postgres
against NFS-mounted data directories. Shane Kerr's paper cited above
mentions some other rather scary properties, including O_EXCL file
creation not really working
On Mon, 2007-10-01 at 19:36 +0100, Simon Riggs wrote:
I *do* think it's an accurate statement that if you're going to use
Postgres, or any other OLTP database, on NFS you'd better have access to
a NAS expert. But to say that it's a bad idea even if you have expert
help is probably
Simon Riggs [EMAIL PROTECTED] writes:
http://blogs.netapp.com/dave/2007/08/oracle-optimize.html
Not a whole lot of technical content there, but pretty interesting
nonetheless. I *think* that the issues we're seeing are largely in the
NFS client-side kernel code, so bypassing that stack as
Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
http://blogs.netapp.com/dave/2007/08/oracle-optimize.html
Not a whole lot of technical content there, but pretty interesting
nonetheless. I *think* that the issues we're seeing are largely in the
NFS client-side kernel code, so
Tom Lane wrote:
If this is what's happening I'd claim it is a kernel bug, but seeing
that I see it on FC6 and Miya sees it on Solaris 10, it would be a bug
widespread enough that we'd not be likely to get it killed off soon.
I think my colleague was solving similar issue in JavaDB. IIRC the
11 matches
Mail list logo
