The pxf_fdw files were removed in Greenplum via this commit[1] in Nov 2022, which indicated that pxf_fdw should be built from the greenplum-db/pxf (cloudberry-pxf) repo.
AFAIS, we don't encourage the users to configure the build with the `--enable-pxf` option in the Cloudberry build. The pxf files in Cloudberry source are deprecated, right? If so, we can remove these files too. Please correct me if I'm wrong. [1]: https://github.com/greenplum-db/gpdb-archive/commit/913de8e1caeb530227298b4db5e829eb521f0780#diff-60b063991ef1dbb96ee2c1dbb034127edf8b2d72cdba7a1561c016003c24a131 Best, Dianjin Wang On Tue, Oct 21, 2025 at 9:18 PM misterraindrop <[email protected]> wrote: > > I am not a developer of PXF. I am trying to contribute to cloudberry-pxf. > Currently, I am merging the latest commits into cloudberry-pxf, but I have > some question > there is a pxf_fdw.c file in cloudberry-pxf, and there is also a pxf_fdw.c > in the cloudberry code. What is the relationship between them? Which one > should I refer to? > > > Additionally, I noticed that external-table has been deprecated. What is the > future status of this module? I have questions regarding how PXF will evolve > in the future, among other similar concerns. > > > > > > > abort issue: > https://github.com/apache/cloudberry/issues/983#issuecomment-2796661810 > https://github.com/apache/cloudberry-pxf/pull/10 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
