From: | strange(at)nsk(dot)yi(dot)org |
---|---|
To: | Andrew Sullivan <andrew(at)libertyrms(dot)info>, PostgresSQL General Mailing List <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Linux Largefile Support In Postgresql RPMS |
Date: | 2002-08-13 18:39:01 |
Message-ID: | 20020813193900.A1800@nsk.yi.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On Tue, Aug 13, 2002 at 02:09:07PM -0400, Andrew Sullivan wrote:
> On Tue, Aug 13, 2002 at 06:45:59PM +0100, strange(at)nsk(dot)yi(dot)org wrote:
>
> > support isn't compiled, I didn't see one occuring from any application
> > having the support, but not the filesystem. (Your "not so standard
>
> Wrong. The symptom is _exactly the same_ if the program doesn't have
> the support, the filesystem doesn't have the support, or both, at
> least on Solaris. I've checked.
??
My point is that: Having postgresql the support doesn't bring NEW errors.
I never said postgresql would automagically gain support on filesystems
that don't support largfiles, I said no one mentioned an error caused by
postgresql *having* the support, but *not the filesystem*. Maybe I wasn't
clear, but I meant *new* errors.
As it seams, adding support to largefiles doesn't break anything.
Regards,
Luciano Rocha
--
Consciousness: that annoying time between naps.
From | Date | Subject | |
---|---|---|---|
Next Message | Jon Swinth | 2002-08-13 18:53:21 | Read Lock For Foreign Key |
Previous Message | Robert L Mathews | 2002-08-13 18:27:48 | extract () and interval formatting |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-08-13 19:03:21 | Re: db partial dumping with pg_dump |
Previous Message | Bruce Momjian | 2002-08-13 18:16:49 | Re: FUNC_MAX_ARGS benchmarks |