Greg Smith wrote:
On Wed, 13 Aug 2008, Ron Mayer wrote:
Second of all - ext3 fsync() appears to me to be *extremely* stupid.
It only seems to correctly do the correct flushing (and waiting) for a
drive's cache to be flushed when a file's inode has changed.
This is bad, but the way PostgreSQL
Hello,
We're developing a project which uses PostgreSQL to store binary
documents. Since our system is likely to grow up to some terabytes in two
years, I'd like to ask if some of you have had some experience with
storing a huge amount of blob files in postgres. How does it scale in
performance?
I've seen it written a couple of times in this thread, and in the
wikipedia article, that SOME sw raid configs don't support write
barriers. This implies that some do. Which ones do and which ones
don't? Does anybody have a list of them?
I was mainly wondering if sw RAID0 on top of hw RAID1 wou
On Wed, 13 Aug 2008, Ron Mayer wrote:
First off - some IDE drives don't even support the relatively recent ATA
command that apparently lets the software know when a cache flush is
complete.
Right, so this is one reason you can't assume barriers will be available.
And barriers don't work rega
"Craig Ringer" <[EMAIL PROTECTED]> writes:
> It strikes me that there are really two types of query hint possible here.
>
> One tells the planner (eg) "prefer a merge join here".
>
> The other gives the planner more information that it might not otherwise
> have to work with, so it can improve its
On Wed, 2008-08-13 at 21:30 -0400, Tom Lane wrote:
> Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> It seems like we'll want to do it somehow. Perhaps the cleanest way is
> >> to incorporate toast-table settings in the reloptions of the parent
> >> table. Otherwise dump/relo
