| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Alvaro Herrera from 2ndQuadrant <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: logical decoding : exceeded maxAllocatedDescs for .spill files |
| Date: | 2019-09-13 16:14:32 |
| Message-ID: | 7005.1568391272@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com> writes:
> You mean tracking excess kernel fds right ? Yeah, we can use VFDs so
> that excess fds are automatically closed. But Alvaro seems to be
> talking in context of tracking of file seek position. VFD does not
> have a mechanism to track file offsets if one of the vfd cached file
> is closed and reopened.
Hm. It used to, but somebody got rid of that on the theory that
we could use pread/pwrite instead. I'm inclined to think that that
was the right tradeoff, but it'd mean that getting logical decoding
to adhere to the VFD API requires extra work to track file position
on the caller side.
Again, though, the advice that's been given here is that we should
fix logical decoding to use the VFD API as it stands, not change
that API. I concur with that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-09-13 16:31:38 | Re: logical decoding : exceeded maxAllocatedDescs for .spill files |
| Previous Message | Alvaro Herrera | 2019-09-13 16:03:06 | Re: [HACKERS] CLUSTER command progress monitor |