jrgemignani commented on PR #2165: URL: https://github.com/apache/age/pull/2165#issuecomment-3563504980
> > > > @optionals Apache AGE **PG18** isn't working with PostgreSQL 18 yet. > > > > > > > > > I used the code from this PR, Isn't this PR just for adapting to PostgreSQL 18? > > > I tried the branch "sanchayanghosh:feature/2164/provide-support-for-postgresql-16-18," and also tried merging it into the latest master code: [571c19](https://github.com/apache/age/commit/571c19) > > > > > > **PG18** is still a test branch and this particular PR currently does not allow PG18 to build with Apache AGE. > > I understand. This issue was discovered in a local development environment. The comments above are simply to report that this PR has this problem. Before merging, it should be verified whether the issue indeed exists, and if so, a targeted fix will be necessary. > > In addition, I used this approach because the issue described in #1722 currently has no suitable solution. If a workaround or an updated fix becomes available, it would be greatly appreciated. After multiple attempts locally, I have not found any alternative besides fully manual SQL construction or using PREPARE as a workaround. @optionals - You may want to try PR #2251. It is another PR to bring PG18 into the fold and it looks good so far. Your test could be valuable there as well. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
