| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
| Cc: | Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Smith <greg(at)2ndquadrant(dot)com>, Amy Smith <vah123(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: postgres external table |
| Date: | 2010-01-19 11:08:42 |
| Message-ID: | 407d949e1001190308i4f66d3aegd7fe25ff696bfd46@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jan 19, 2010 at 4:41 AM, Craig Ringer
<craig(at)postnewspapers(dot)com(dot)au> wrote:
> How can that work without a transactional file system, though? If the
> external process writes to the file while you're half-way through reading
> it, what's the database to do? In general, how do external tables cope with
> the fact that they're on non-transactional storage?
Well if you use mv to replace the old file with the new one then it
should be safe. Unless your query involves opening the table multiple
times or your transactions are more complex than a single query...
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jayadevan M | 2010-01-19 11:16:00 | Re: postgres external table |
| Previous Message | Alban Hertroys | 2010-01-19 10:57:31 | Re: Index on immutable function call |