>
>
> Ahh. I think you can use this effectively but not the way you're
> describing.
>
> Instead of writing the wal directly to persistentFS what I think you're
> better
> off doing is treating persistentFS as your backup storage. Use "Archiving"
> as
> described here to archive the WAL files to pe
>
>
> Wow, this is a fascinating situation. Are you sure the fsyncs are the only
> thing to worry about though? Postgres will call write(2) many times even if
> you disabled fsync entirely. Surely the kernel and filesystem will
> eventually
> send some of them through even if no fsyncs arrive?
>
G
>
>
>> Are you sure this will work correctly for database use at all? The known
> issue listed at
> http://www.persistentfs.com/documentation/Release_Notessounded like a much
> bigger consistancy concern than the fsync trivia you're
> bringing up:
>
> "In the current Technology Preview release,
> Running without fsyncs is likely to lead to a corrupted db if you get
> a crash / loss of connection etc...
>
Just to clarify, by corrupted db you mean that all information (even the
ones prior to the last fsync) will be lost. Right?
Thanks,
Ram
Hey,
I am running a postgresql server on Amazon EC2. My current plan is to mount
an Amazon S3 bucket as a drive using PersistentFS which is a POSIX-compliant
file system.
I will be using this for write-ahead-logging. The issue with S3 is that
though the actual storage is cheap, they charge $1 per 1
Hi,
By default, my postgresql server is set to use UTF8 character set. I was
wondering if there is any way to make sure that certain fields like url etc.
only makes use of ascii. My main aim is to save space by using only 1 byte /
character for urls (some of the urls are over 200 characters long)
Hi,
I am deciding between MySQL and Postgres. I'm leaning towards Postgres
mainly due the widely publicized speed when using transactions. However, I
am not able to find any good books / resources for tuning/ optimizing the
database. Is there a book like "High Performance MySQL" for Postgres that
Thanks for the quick response. And I assume that primary key
uniqueness is not tested across tables. Right?
Thanks,
Ram
On Fri, Mar 21, 2008 at 8:59 PM, Erik Jones <[EMAIL PROTECTED]> wrote:
> On Mar 21, 2008, at 7:15 PM, Ram Ravichandran wrote:
>
> > Hey,
> >
> &g
Hey,
Suppose I have a table with the following fields:
CREATE TABLE distributors (
id DECIMAL(3) PRIMARY KEY,
nameVARCHAR(40),
status INTEGER
);
I would ike to partition this table based on status which can be [0,1,2,3,4].
I was wondering if the records can change their
