You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@age.apache.org by "JamesInform (via GitHub)" <gi...@apache.org> on 2024/09/15 18:20:32 UTC
[I] PostgreSQL 17 not supported [age]
JamesInform opened a new issue, #2111:
URL: https://github.com/apache/age/issues/2111
Hi all
I built age for PostgreSQL 17. Basically compiling worked without errors.
But when I try to create the extension I get the following error:
<img width="887" alt="image" src="https://github.com/user-attachments/assets/daf96f0f-cbf9-4660-b752-78d72b296a7a">
When will a PostgreSQL 17 compatible version of age be available?
Cheers,
James
--
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: dev-unsubscribe@age.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2644658842
@thomastthai Unfortunately, the following is not true and is still ongoing -
> Good to know ASF and AGEDB worked things out.
The Apache AGE PMC, in particular the chair (Jeff J.) and the ASF, are still working to bring the above mentioned issues to a resolution. I mention this because -
> I'm curious how involved Jeff Jirsa, AGE Committee Chair, has been since their appointment in July 2024.
Jeff has spent **a lot of time**, as have the other ASF and PMC members, (through approved Apache channels) since said date to attempt to bring said issues to a resolution. Unfortunately, engagement on these issues takes valuable time away from many other activities. As these channels are not privy to all, don't let appearances suggest a lack of involvement or engagement.
Also, please remember the following -
- > but everyone is a volunteer, so best effort and no promises of timelines
Each Apache member has their own schedule and level of engagement. This was something we (Apache AGE) learned through incubation and is the Apache way.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2951584851
@dianaoa22 We've been working on PG17 the past few days. Unfortunately, there have been issues with the CI that need to be fixed first.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-3353213866
@MuhammadTahaNaveed Is this something that you could answer?
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "grmkris (via GitHub)" <gi...@apache.org>.
grmkris commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2642350868
ai coding agents can't come soon enough... 🫡 🤣
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2441910016
I was thinking of closing this issue, but I will leave it open for comments or inquiries.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "knutole (via GitHub)" <gi...@apache.org>.
knutole commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2643707068
@thomastthai That's great!
I found the [minutes](https://whimsy.apache.org/board/minutes/AGE.html) (scroll down on the linked page). Project went from "super healthy" in May 2024 to "stagnant" in November 2024, although they do not state any reason for the stagnation. Next meeting is scheduled for February 2025. Would probably be good to file a proper request for expanding write access to more groups by then.
As for ongoing issues between Apache AGE and BitNine, there are mentions in the minutes to some copyright conflict, regarding use of name and logo, and per minutes it was being resolved. Perhaps there are other issues on top. Conflicts aside, BitNine certainly seems like a good candidate for getting write access, as they have a product being built on top of Apache AGE, from what I understand. There might be others.
Minutes from last three meetings:
> # [20 Nov 2024](http://apache.org/foundation/records/minutes/2024/board_minutes_2024_11_20.txt) [Jeff Jirsa]
>
> ## Description:
> The mission of Apache AGE is the creation and maintenance of software related
> to a multi-model database that enables graph and relational models built on
> PostgreSQL
>
> ## Project Status:
> Current project status: Ongoing, but with reducing velocity
> Issues for the board: None
>
> ## Membership Data:
> Apache AGE was founded 2022-05-17 (2 years ago)
> There are currently 18 committers and 12 PMC members in this project.
> The Committer-to-PMC ratio is 3:2.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was Rafsun Masud on 2024-01-28.
> - No new committers. Last addition was Zainab Saad on 2024-01-31.
>
> ## Project Activity:
> Project activity is at a local minimum - there have been zero commits to the
> project since September. While GitHub issues are being opened, actual project
> activity (bug fixes, PR merging) has begun to stagnate.
>
> ## Community Health:
> While GitHub issues are being opened, actual project activity (bug fixes, PR
> merging) has begun to stagnate.
>
> # [21 Aug 2024](http://apache.org/foundation/records/minutes/2024/board_minutes_2024_08_21.txt) [Jeff Jirsa / Rich]
> ## Description:
> The mission of Apache AGE is the creation and maintenance of software related
> to a multi-model database that enables graph and relational models built on
> PostgreSQL
>
> ## Project Status:
> Current project status: Ongoing
>
> Issues for the board: Acknowledging for the record that the PMC chair was
> changed by Board resolution in June 2024. The new PMC chair is coming up to
> speed.
>
> ## Membership Data:
> Apache AGE was founded 2022-05-17 (2 years ago)
> There are currently 19 committers and 12 PMC members in this project.
> The Committer-to-PMC ratio is roughly 3:2.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was Rafsun Masud on 2024-01-28.
> - No new committers. Last addition was Zainab Saad on 2024-01-31.
>
> ## Project Activity:
>
> Recent releases:
> PG11-1.5.0 was released on 2024-03-19.
> PG12-1.5.0 was released on 2024-03-11.
> PG13-1.5.0 was released on 2024-02-29.
> PG14-1.5.0 was released on 2024-02-16.
> PG15-1.5.0 was released on 2024-02-06.
> PG16-1.5.0 was released on 2024-01-26.
>
>
> ## Community Health:
> Contributions remain consistent at a quarter-by-quarter view, with
> approximately 40-50 code commits per quarter, though contributions
> tend to be cyclical, and local-minima are observed. There exists a
> sufficient number of PMC members replying to emails to manage the
> project.
>
> # [15 May 2024](http://apache.org/foundation/records/minutes/2024/board_minutes_2024_05_15.txt) [Eya Badal / Jeff]
> ## Description:
> The mission of Apache AGE is the creation and maintenance of software related
> to a multi-model database that enables graph and relational models built on
> PostgreSQL.
>
> ## Project Status:
> Current project status: Ongoing with high activity.
>
> Issues for the board: There are some trademark issues that PMCs are currently
> trying to resolve. An official email has been sent to the AGEDB team and there
> have been a couple of attempts to fix the issues. The AGEDB team has already
> fixed a few of the issues and is currently working with the ASF trademark team
> to resolve the remaining problems such as the logo, name and others. In their
> response (tradmeark CC ed), they mentioned that they have already started and
> initiated the official process of renaming the company from AGEDB.
>
> ## Membership Data:
> Apache AGE was founded 2022-05-17 (2 years ago)
> There are currently 20 committers and 14 PMC members in this project.
> The Committer-to-PMC ratio is roughly 5:4.
>
> Community changes, past quarter:
> - No new PMC members. Last addition was Rafsun Masud on 2024-01-28.
> - No new committers. Last addition was Zainab Saad on 2024-01-31.
>
> ## Project Activity:
> Recent releases: PG11-1.5.0 was released on 2024-03-19. PG12-1.5.0 was
> released on 2024-03-11. PG13-1.5.0 was released on 2024-02-29. PG14-1.5.0 was
> released on 2024-02-16.
>
> We submitted a couple of papers for different conferences.
>
> ## Community Health:
> The project is super healthy. The dev@age.apache.org had a
> 112% increase in traffic in the past quarter (660 emails compared to 310).
> Community Health Score (Chi): 9.60 (Super Healthy)
> @Justin: follow up with AGE PMC about corporate branding issue
>
> @Justin: follow up with Docker distribution
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2735199625
@MuhammadTahaNaveed Does **PG17_prepare** look good to be renamed to **PG17**? Thoughts?
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "uhayat (via GitHub)" <gi...@apache.org>.
uhayat commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2467589786
@df7cb nice to see that.
I wish there is similar setup for PGDG Yum as well. I see there is directory for age in rpm repo but never seen live RPMs. I guess I need to contact Devrim to check status. if there is any blocker or some patch I may provide. I will create a separate issue for tracking.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "grmkris (via GitHub)" <gi...@apache.org>.
grmkris commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2519738805
thanks you @uhayat
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "uhayat (via GitHub)" <gi...@apache.org>.
uhayat commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2442897079
@jrgemignani thanks for the review. I agree that PR only fixed the compilation problem mention in the ticket but does not cover the whole PG 17 support. I will see if i can come up with full support. Based on the change we can see if it needs a separate branch for PG 17 or not. I will update here.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani closed issue #2111: PostgreSQL 17 not supported
URL: https://github.com/apache/age/issues/2111
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "df7cb (via GitHub)" <gi...@apache.org>.
df7cb commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2441920997
@jrgemignani thanks for the honest info.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "knutole (via GitHub)" <gi...@apache.org>.
knutole commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2642776446
> [@knutole](https://github.com/knutole), [@jrgemignani](https://github.com/jrgemignani)'s statement was clear. The team paid to work on AGE was let go — most likely because funding ran out or shifted to other priorities. Whatever the reason, he summarized the future direction below:
>
> > Currently, there isn't an eta for, nor a roadmap to, an Apache AGE version for PG17 **or any continuing support**.
>
> Paid work for an open source can accelerate a project until the money, passion, or time runs out. It sucks, as AGE is one of the more exciting projects for PostgreSQL.
I don't accept that an open source Apache project, which many people use and contribute to, can just "shut down" without proper explanation and future planning.
It seems that the main contributor @jrgemignani was made redundant at BitNine, and [Apache Committee](https://projects.apache.org/committee.html?age) which "owns" the repo (and thus the write access) has not passed the torch to someone else. More info here: https://github.com/bitnine-oss/agensgraph/issues/663#issuecomment-2642724649
Seems that the Apache AGE Committee should be called upon to pass the torch on this project.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2643620381
@jirutka @thomastthai @df7cb @uhayat I have created a branch, based off of the current **master**, called **PG17_prepare**.
Please apply your PRs, to allow AGE for PG17 to compile, to that branch. When we can validate that **PG17_prepare** compiles cleanly, I can make it **PG17**.
Btw, it will take me a moment to set up Docker for the above changes.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "dianaoa22 (via GitHub)" <gi...@apache.org>.
dianaoa22 commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2951358833
Is there an updated timeline for when Apache AGE will officially support PostgreSQL 17 in the 1.5.0 release?
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "webcodes-cz (via GitHub)" <gi...@apache.org>.
webcodes-cz commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-3257365990
@jrgemignani Hello, I would like to ask if it will be done any time soon. Thanks for your hard work.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-3357958488
@xeroxnir Can you please create a new discussion/issue for this over on [ https://github.com/apache/age-viewer/ ](https://github.com/apache/age-viewer/ ) this space is specifically for AGE.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "uhayat (via GitHub)" <gi...@apache.org>.
uhayat commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2378669165
@JamesInform I created a PR ([2118](https://github.com/apache/age/pull/2118)) to resolve this issue. Currently there is no separate branch for branch for PG17, so I added PG17 version number check.
@jrgemignani do we have a plan when should be create a separate branch, or who could create separate branch, or should this PR merged to master as is?
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "nicholasveloso (via GitHub)" <gi...@apache.org>.
nicholasveloso commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2555118156
> @JamesInform @df7cb Currently, there isn't an eta for, nor a roadmap to, an Apache AGE version for PG17 or any continuing support. The core R&D team that was driving Apache AGE (paid to work on this project) was eliminated earlier this month.
>
> This means that future features, updates, bug fixes, etc. will be at a lot slower pace, if at all. Unfortunately, I cannot coerce or hold volunteers to any particular schedule.
Is there any new news about this issue?
Is Apache AGE project dead?
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jirutka (via GitHub)" <gi...@apache.org>.
jirutka commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2450172099
This means I have to drop postgresql-age from the upcoming Alpine Linux v3.21. :(
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "df7cb (via GitHub)" <gi...@apache.org>.
df7cb commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2441084857
It's not ready for PG17 yet. Running the regression tests against PG17:
```
2024-10-28 09:43:48.644 UTC client backend[346252] pg_regress/expr ERROR: labels() argument must be a vertex
2024-10-28 09:43:48.644 UTC client backend[346252] pg_regress/expr STATEMENT: SELECT * from cypher('list', $$RETURN labels("string")$$) as (Labels agtype);
TRAP: failed Assert("HeapTupleIsValid(proctup)"), File: "src/backend/utils/ag_func.c", Line: 48, PID: 346252
postgres: myon contrib_regression [local] SELECT(ExceptionalCondition+0x75) [0x555e07a0fe45]
/usr/lib/postgresql/17/lib/age.so(+0x5be85) [0x7f0b17033e85]
/usr/lib/postgresql/17/lib/age.so(+0x2a04b) [0x7f0b1700204b]
postgres: myon contrib_regression [local] SELECT(range_table_entry_walker_impl+0x26) [0x555e077458b6]
postgres: myon contrib_regression [local] SELECT(range_table_walker_impl+0x6a) [0x555e07745a2a]
/usr/lib/postgresql/17/lib/age.so(+0x2ac0f) [0x7f0b17002c0f]
postgres: myon contrib_regression [local] SELECT(parse_analyze_fixedparams+0xac) [0x555e075f4a2c]
postgres: myon contrib_regression [local] SELECT(pg_analyze_and_rewrite_fixedparams+0x2a) [0x555e078b2b4a]
postgres: myon contrib_regression [local] SELECT(+0x55b193) [0x555e078b3193]
postgres: myon contrib_regression [local] SELECT(PostgresMain+0x161f) [0x555e078b4ccf]
postgres: myon contrib_regression [local] SELECT(BackendMain+0x51) [0x555e078af321]
postgres: myon contrib_regression [local] SELECT(postmaster_child_launch+0xc8) [0x555e07805bf8]
postgres: myon contrib_regression [local] SELECT(+0x4b1d0a) [0x555e07809d0a]
postgres: myon contrib_regression [local] SELECT(PostmasterMain+0xe8c) [0x555e0780bb9c]
postgres: myon contrib_regression [local] SELECT(main+0x20a) [0x555e074d12aa]
/lib/x86_64-linux-gnu/libc.so.6(+0x29d68) [0x7f0b22c33d68]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f0b22c33e25]
postgres: myon contrib_regression [local] SELECT(_start+0x21) [0x555e074d1871]
2024-10-28 09:43:50.074 UTC postmaster[346211] LOG: server process (PID 346252) was terminated by signal 6: Aborted
2024-10-28 09:43:50.074 UTC postmaster[346211] DETAIL: Failed process was running: SELECT * FROM json('1');
```
AGE is one of the last PostgreSQL packages in Debian not yet supporting PG17 yet, so getting this fixed would be appreciated. Thanks.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "df7cb (via GitHub)" <gi...@apache.org>.
df7cb commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2642405738
As said above, including #2130 will make the 16 branch support 17 as well. That's what we did for the Debian packages.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2645867791
@nicholasveloso I am working with a few others to get PG17 support for version 1.5.0, hopefully, by the end of the month; maybe only as a branch and not an official release. Full releases take a lot of work and PMC input and can only be done by members with specific access.
- > but everyone is a volunteer, so best effort and no promises of timelines
As to future development, some of us are working on what can be done. Again, -
- > but everyone is a volunteer, so best effort and no promises of timelines
I cannot stress this last point enough.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2645863649
@thomastthai Issues, like this one about PG17, are not really the correct forum for subjects, or summaries, like internal Apache discussions.
I initially added to this thread to give everyone a heads up for future development. My follow up was only to let others know that we are currently working on issues in the background.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-3138157374
@thomastthai PG 17 is on the **PG17** branch and is current with the **master**. So, if you want to use PG17.5 that branch should work for you.
Currently, I have started working on building the official release of 1.6.0 for PG17
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2787112555
@uhayat
> what would be next step to officially release AGE 1.5.0 for PG 17?
The next step is pending on others. I, unfortunately, cannot do everything -
> **PG17_prepare** has been renamed to **PG17** and I created a Docker Hub **PG17** build.
After that is done, and verified to be good, then the **master** branch needs to be brought in line with **PG17**, as all new work needs to be aligned with **PG17**. **PG17** can then go through a release. However, it would **not** be for version **1.5.0** as **PG17** is built off of the current **master** branch, which has a lot of work added since **1.5.0**. We would likely make **PG17** version **1.6.0**.
As for the release, I can do it, but I cannot do any of the voting.
After **PG17** version **1.6.0** has been released, or possibly before, we would need to release **1.6.0** for **PG16**, **PG15**, **PG14**, & **PG13**.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-3266783418
@webcodes-cz Support is ready for PG17 1.6.0, it will be released after PG16 1.6.0 is released.
The [DISCUSS] thread for PG16 1.6.0 was opened this past Thursday [https://lists.apache.org/list.html?dev@age.apache.org](https://lists.apache.org/list.html?dev@age.apache.org)
Provided everything goes well with PG16's release, PG17 should start within 2 weeks.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "uhayat (via GitHub)" <gi...@apache.org>.
uhayat commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2461522057
Hi,
A new PR is create (https://github.com/apache/age/pull/2130) for PG 17 support and tested locally on multiple environment.
Feedback would be appreciated.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "knutole (via GitHub)" <gi...@apache.org>.
knutole commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2643973783
Thanks a lot for the good info @jrgemignani 👍
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "thomastthai (via GitHub)" <gi...@apache.org>.
thomastthai commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2643534062
I couldn't find the [minutes](https://projects.apache.org/committee.html?age) from the [Apache AGE committee](https://projects.apache.org/committee.html?age) meetings or a way to contact the committee members. I emailed their data maintainer, Eya Badal, to get support. If the situation is unchanged after this month, the next step is to contact the Apache Foundation and their sponsors. The Apache AGE repo needs additional active contributors with write access to move the project forward.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "brecke (via GitHub)" <gi...@apache.org>.
brecke commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-3083215268
any news on this front? I see there's a branch (behind master) PG17 and a docker-container, but it would be great to have a proper official release soon, if possible. Is there an ETA for a new release supporting PG17?
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2441859526
@uhayat
This is the problem with attempting to add fixes to a version (PG16 in this case) to allow it to run on another version (PG17 in this case) without checking to see if it actually fixes the newer version. I mistakenly assumed that this was done.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani closed issue #2111: PostgreSQL 17 not supported
URL: https://github.com/apache/age/issues/2111
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "GreenZeeGuy (via GitHub)" <gi...@apache.org>.
GreenZeeGuy commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2803200123
> For anyone interested, I’ve packed RPM packages of Apache AGE for PostgreSQL 13–17 on EL-based systems, with support for both `x86_64` and `aarch64`. Feel free to check them out!
>
> https://pigsty.io/ext/feat/age/
>
> OS Arch **PG17** **PG16** **PG15** **PG14** **PG13**
> `el8` `x86_64` [**`apache-age_17`**](https://repo.pigsty.io/yum/pgsql/el8.x86_64/apache-age_17-1.5.0-2PIGSTY.el8.x86_64.rpm) **PIGSTY** 1.5.0 [**`apache-age_16`**](https://repo.pigsty.io/yum/pgsql/el8.x86_64/apache-age_16-1.5.0-2PIGSTY.el8.x86_64.rpm) **PIGSTY** 1.5.0 [**`apache-age_15`**](https://repo.pigsty.io/yum/pgsql/el8.x86_64/apache-age_15-1.5.0-2PIGSTY.el8.x86_64.rpm) **PIGSTY** 1.5.0 [**`apache-age_14`**](https://repo.pigsty.io/yum/pgsql/el8.x86_64/apache-age_14-1.5.0-2PIGSTY.el8.x86_64.rpm) **PIGSTY** 1.5.0 [**`apache-age_13`**](https://repo.pigsty.io/yum/pgsql/el8.x86_64/apache-age_13-1.5.0-2PIGSTY.el8.x86_64.rpm) **PIGSTY** 1.5.0
> `el8` `aarch64` [**`apache-age_17`**](https://repo.pigsty.io/yum/pgsql/el8.aarch64/apache-age_17-1.5.0-2PIGSTY.el8.aarch64.rpm) **PIGSTY** 1.5.0 [**`apache-age_16`**](https://repo.pigsty.io/yum/pgsql/el8.aarch64/apache-age_16-1.5.0-2PIGSTY.el8.aarch64.rpm) **PIGSTY** 1.5.0 [**`apache-age_15`**](https://repo.pigsty.io/yum/pgsql/el8.aarch64/apache-age_15-1.5.0-2PIGSTY.el8.aarch64.rpm) **PIGSTY** 1.5.0 [**`apache-age_14`**](https://repo.pigsty.io/yum/pgsql/el8.aarch64/apache-age_14-1.5.0-2PIGSTY.el8.aarch64.rpm) **PIGSTY** 1.5.0 [**`apache-age_13`**](https://repo.pigsty.io/yum/pgsql/el8.aarch64/apache-age_13-1.5.0-2PIGSTY.el8.aarch64.rpm) **PIGSTY** 1.5.0
> `el9` `x86_64` [**`apache-age_17`**](https://repo.pigsty.io/yum/pgsql/el9.x86_64/apache-age_17-1.5.0-2PIGSTY.el9.x86_64.rpm) **PIGSTY** 1.5.0 [**`apache-age_16`**](https://repo.pigsty.io/yum/pgsql/el9.x86_64/apache-age_16-1.5.0-2PIGSTY.el9.x86_64.rpm) **PIGSTY** 1.5.0 [**`apache-age_15`**](https://repo.pigsty.io/yum/pgsql/el9.x86_64/apache-age_15-1.5.0-2PIGSTY.el9.x86_64.rpm) **PIGSTY** 1.5.0 [**`apache-age_14`**](https://repo.pigsty.io/yum/pgsql/el9.x86_64/apache-age_14-1.5.0-2PIGSTY.el9.x86_64.rpm) **PIGSTY** 1.5.0 [**`apache-age_13`**](https://repo.pigsty.io/yum/pgsql/el9.x86_64/apache-age_13-1.5.0-2PIGSTY.el9.x86_64.rpm) **PIGSTY** 1.5.0
> `el9` `aarch64` [**`apache-age_17`**](https://repo.pigsty.io/yum/pgsql/el9.aarch64/apache-age_17-1.5.0-2PIGSTY.el9.aarch64.rpm) **PIGSTY** 1.5.0 [**`apache-age_16`**](https://repo.pigsty.io/yum/pgsql/el9.aarch64/apache-age_16-1.5.0-2PIGSTY.el9.aarch64.rpm) **PIGSTY** 1.5.0 [**`apache-age_15`**](https://repo.pigsty.io/yum/pgsql/el9.aarch64/apache-age_15-1.5.0-2PIGSTY.el9.aarch64.rpm) **PIGSTY** 1.5.0 [**`apache-age_14`**](https://repo.pigsty.io/yum/pgsql/el9.aarch64/apache-age_14-1.5.0-2PIGSTY.el9.aarch64.rpm) **PIGSTY** 1.5.0 [**`apache-age_13`**](https://repo.pigsty.io/yum/pgsql/el9.aarch64/apache-age_13-1.5.0-2PIGSTY.el9.aarch64.rpm) **PIGSTY** 1.5.0
> `d12` `x86_64` [**`postgresql-17-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-17-age_1.5.0~rc0-3.pgdg120+2_arm64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-16-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-16-age_1.5.0~rc0-3.pgdg120+2_arm64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-15-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-15-age/postgresql-15-age_1.5.0~rc0-1.pgdg120+2_arm64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-14-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-14-age/postgresql-14-age_1.5.0~rc0-1.pgdg120+2_arm64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-13-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-13-age/postgresql-13-age_1.5.0~rc0-1.pgdg120+1_arm64.deb) **PGDG** 1.5.0~rc0
> `d12` `aarch64` [**`postgresql-17-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-17-age_1.5.0~rc0-3.pgdg120+2_amd64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-16-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-16-age_1.5.0~rc0-3.pgdg120+2_amd64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-15-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-15-age/postgresql-15-age_1.5.0~rc0-1.pgdg120+2_amd64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-14-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-14-age/postgresql-14-age_1.5.0~rc0-1.pgdg120+2_amd64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-13-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-13-age/postgresql-13-age_1.5.0~rc0-1.pgdg120+1_amd64.deb) **PGDG** 1.5.0~rc0
> `u22` `x86_64` [**`postgresql-17-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-17-age_1.5.0~rc0-3.pgdg22.04+2_amd64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-16-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-16-age_1.5.0~rc0-3.pgdg22.04+2_amd64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-15-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-15-age/postgresql-15-age_1.5.0~rc0-1.pgdg22.04+2_amd64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-14-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-14-age/postgresql-14-age_1.5.0~rc0-1.pgdg22.04+2_amd64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-13-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-13-age/postgresql-13-age_1.5.0~rc0-1.pgdg22.04+1_amd64.deb) **PGDG** 1.5.0~rc0
> `u22` `aarch64` [**`postgresql-17-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-17-age_1.5.0~rc0-3.pgdg22.04+2_arm64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-16-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-16-age_1.5.0~rc0-3.pgdg22.04+2_arm64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-15-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-15-age/postgresql-15-age_1.5.0~rc0-1.pgdg22.04+2_arm64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-14-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-14-age/postgresql-14-age_1.5.0~rc0-1.pgdg22.04+2_arm64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-13-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-13-age/postgresql-13-age_1.5.0~rc0-1.pgdg22.04+1_arm64.deb) **PGDG** 1.5.0~rc0
> `u24` `x86_64` [**`postgresql-17-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-17-age_1.5.0~rc0-3.pgdg24.04+2_amd64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-16-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-16-age_1.5.0~rc0-3.pgdg24.04+2_amd64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-15-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-15-age/postgresql-15-age_1.5.0~rc0-1.pgdg24.04+2_amd64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-14-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-14-age/postgresql-14-age_1.5.0~rc0-1.pgdg24.04+2_amd64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-13-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-13-age/postgresql-13-age_1.5.0~rc0-1.pgdg24.04+1_amd64.deb) **PGDG** 1.5.0~rc0
> `u24` `aarch64` [**`postgresql-17-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-17-age_1.5.0~rc0-3.pgdg24.04+2_arm64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-16-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-16-age_1.5.0~rc0-3.pgdg24.04+2_arm64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-15-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-15-age/postgresql-15-age_1.5.0~rc0-1.pgdg24.04+2_arm64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-14-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-14-age/postgresql-14-age_1.5.0~rc0-1.pgdg24.04+2_arm64.deb) **PGDG** 1.5.0~rc0 [**`postgresql-13-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-13-age/postgresql-13-age_1.5.0~rc0-1.pgdg24.04+1_arm64.deb) **PGDG** 1.5.0~rc0
Minor typo in the table :
d12 x86_64 and d12 aarch64 need to be swapped
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-3085313759
@brecke I am working on it, just swamped with other tasks atm.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "Vonng (via GitHub)" <gi...@apache.org>.
Vonng commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2742920337
For anyone interested, I’ve packed RPM packages of Apache AGE for PostgreSQL 13–17 on EL-based systems, with support for both `x86_64` and `aarch64`. Feel free to check them out!
https://pigsty.io/ext/feat/age/
| OS | Arch | **PG17** | **PG16** | **PG15** | **PG14** | **PG13** |
| :---: | :-------: | :----------------------------------------------------------: | :----------------------------------------------------------: | :----------------------------------------------------------: | :----------------------------------------------------------: | :----------------------------------------------------------: |
| `el8` | `x86_64` | [**`apache-age_17`**](https://repo.pigsty.io/yum/pgsql/el8.x86_64/apache-age_17-1.5.0-2PIGSTY.el8.x86_64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_16`**](https://repo.pigsty.io/yum/pgsql/el8.x86_64/apache-age_16-1.5.0-2PIGSTY.el8.x86_64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_15`**](https://repo.pigsty.io/yum/pgsql/el8.x86_64/apache-age_15-1.5.0-2PIGSTY.el8.x86_64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_14`**](https://repo.pigsty.io/yum/pgsql/el8.x86_64/apache-age_14-1.5.0-2PIGSTY.el8.x86_64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_13`**](https://repo.pigsty.io/yum/pgsql/el8.x86_64/apache-age_13-1.5.0-2PIGSTY.el8.x86_64.rpm) **PIGSTY** 1.5.0 |
| `el8` | `aarch64` | [**`apache-age_17`**](https://repo.pigsty.io/yum/pgsql/el8.aarch64/apache-age_17-1.5.0-2PIGSTY.el8.aarch64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_16`**](https://repo.pigsty.io/yum/pgsql/el8.aarch64/apache-age_16-1.5.0-2PIGSTY.el8.aarch64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_15`**](https://repo.pigsty.io/yum/pgsql/el8.aarch64/apache-age_15-1.5.0-2PIGSTY.el8.aarch64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_14`**](https://repo.pigsty.io/yum/pgsql/el8.aarch64/apache-age_14-1.5.0-2PIGSTY.el8.aarch64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_13`**](https://repo.pigsty.io/yum/pgsql/el8.aarch64/apache-age_13-1.5.0-2PIGSTY.el8.aarch64.rpm) **PIGSTY** 1.5.0 |
| `el9` | `x86_64` | [**`apache-age_17`**](https://repo.pigsty.io/yum/pgsql/el9.x86_64/apache-age_17-1.5.0-2PIGSTY.el9.x86_64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_16`**](https://repo.pigsty.io/yum/pgsql/el9.x86_64/apache-age_16-1.5.0-2PIGSTY.el9.x86_64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_15`**](https://repo.pigsty.io/yum/pgsql/el9.x86_64/apache-age_15-1.5.0-2PIGSTY.el9.x86_64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_14`**](https://repo.pigsty.io/yum/pgsql/el9.x86_64/apache-age_14-1.5.0-2PIGSTY.el9.x86_64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_13`**](https://repo.pigsty.io/yum/pgsql/el9.x86_64/apache-age_13-1.5.0-2PIGSTY.el9.x86_64.rpm) **PIGSTY** 1.5.0 |
| `el9` | `aarch64` | [**`apache-age_17`**](https://repo.pigsty.io/yum/pgsql/el9.aarch64/apache-age_17-1.5.0-2PIGSTY.el9.aarch64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_16`**](https://repo.pigsty.io/yum/pgsql/el9.aarch64/apache-age_16-1.5.0-2PIGSTY.el9.aarch64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_15`**](https://repo.pigsty.io/yum/pgsql/el9.aarch64/apache-age_15-1.5.0-2PIGSTY.el9.aarch64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_14`**](https://repo.pigsty.io/yum/pgsql/el9.aarch64/apache-age_14-1.5.0-2PIGSTY.el9.aarch64.rpm) **PIGSTY** 1.5.0 | [**`apache-age_13`**](https://repo.pigsty.io/yum/pgsql/el9.aarch64/apache-age_13-1.5.0-2PIGSTY.el9.aarch64.rpm) **PIGSTY** 1.5.0 |
| `d12` | `x86_64` | [**`postgresql-17-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-17-age_1.5.0~rc0-3.pgdg120+2_arm64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-16-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-16-age_1.5.0~rc0-3.pgdg120+2_arm64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-15-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-15-age/postgresql-15-age_1.5.0~rc0-1.pgdg120+2_arm64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-14-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-14-age/postgresql-14-age_1.5.0~rc0-1.pgdg120+2_arm64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-13-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-13-age/postgresql-13-age_1.5.0~rc0-1.pgdg120+1_arm64.deb) **PGDG** 1.5.0~rc0 |
| `d12` | `aarch64` | [**`postgresql-17-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-17-age_1.5.0~rc0-3.pgdg120+2_amd64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-16-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-16-age_1.5.0~rc0-3.pgdg120+2_amd64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-15-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-15-age/postgresql-15-age_1.5.0~rc0-1.pgdg120+2_amd64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-14-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-14-age/postgresql-14-age_1.5.0~rc0-1.pgdg120+2_amd64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-13-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-13-age/postgresql-13-age_1.5.0~rc0-1.pgdg120+1_amd64.deb) **PGDG** 1.5.0~rc0 |
| `u22` | `x86_64` | [**`postgresql-17-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-17-age_1.5.0~rc0-3.pgdg22.04+2_amd64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-16-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-16-age_1.5.0~rc0-3.pgdg22.04+2_amd64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-15-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-15-age/postgresql-15-age_1.5.0~rc0-1.pgdg22.04+2_amd64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-14-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-14-age/postgresql-14-age_1.5.0~rc0-1.pgdg22.04+2_amd64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-13-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-13-age/postgresql-13-age_1.5.0~rc0-1.pgdg22.04+1_amd64.deb) **PGDG** 1.5.0~rc0 |
| `u22` | `aarch64` | [**`postgresql-17-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-17-age_1.5.0~rc0-3.pgdg22.04+2_arm64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-16-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-16-age_1.5.0~rc0-3.pgdg22.04+2_arm64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-15-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-15-age/postgresql-15-age_1.5.0~rc0-1.pgdg22.04+2_arm64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-14-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-14-age/postgresql-14-age_1.5.0~rc0-1.pgdg22.04+2_arm64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-13-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-13-age/postgresql-13-age_1.5.0~rc0-1.pgdg22.04+1_arm64.deb) **PGDG** 1.5.0~rc0 |
| `u24` | `x86_64` | [**`postgresql-17-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-17-age_1.5.0~rc0-3.pgdg24.04+2_amd64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-16-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-16-age_1.5.0~rc0-3.pgdg24.04+2_amd64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-15-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-15-age/postgresql-15-age_1.5.0~rc0-1.pgdg24.04+2_amd64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-14-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-14-age/postgresql-14-age_1.5.0~rc0-1.pgdg24.04+2_amd64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-13-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-13-age/postgresql-13-age_1.5.0~rc0-1.pgdg24.04+1_amd64.deb) **PGDG** 1.5.0~rc0 |
| `u24` | `aarch64` | [**`postgresql-17-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-17-age_1.5.0~rc0-3.pgdg24.04+2_arm64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-16-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-16-age/postgresql-16-age_1.5.0~rc0-3.pgdg24.04+2_arm64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-15-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-15-age/postgresql-15-age_1.5.0~rc0-1.pgdg24.04+2_arm64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-14-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-14-age/postgresql-14-age_1.5.0~rc0-1.pgdg24.04+2_arm64.deb) **PGDG** 1.5.0~rc0 | [**`postgresql-13-age`**](https://apt.postgresql.org/pub/repos/apt/pool/main/p/postgresql-13-age/postgresql-13-age_1.5.0~rc0-1.pgdg24.04+1_arm64.deb) **PGDG** 1.5.0~rc0 |
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "uhayat (via GitHub)" <gi...@apache.org>.
uhayat commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2785047418
@jrgemignani what would be next step to officially release AGE 1.5.0 for PG 17?
I understand based on commitment of contributor It could be slow process but IMO someone need to start that process. **Personally** I am willing to participate and coordinate for release process, though I am only contributor and not committer and PMC, I am not sure how much I would be able to contribute in **Release** process.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "thomastthai (via GitHub)" <gi...@apache.org>.
thomastthai commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2645927450
@jrgemignani, agreed that Issues isn't the place to discuss subjects, or summaries, like internal Apache discussions. The discussion from "PostgreSQL 17 not supported" evolved organically and your added context added clarity. A summary posted on Discussions would clarify for others who've not read this issue. Thank you again for your input and ongoing volunteer work.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "df7cb (via GitHub)" <gi...@apache.org>.
df7cb commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2461902634
@uhayat works excellently, thanks!
https://pgdgbuild.dus.dg-i.net/job/postgresql-16-age-binaries/12/ (PG16+17, despite the name)
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "thomastthai (via GitHub)" <gi...@apache.org>.
thomastthai commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-3138153284
Which branch should I use if I want to run AGE with PostgreSQL 17.5? I saw the PG17 branch but wasn't sure. Master/main branch compiled and installed fine. I've not run tests on it yet.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2956086580
We were able to fix the CI issues with PG17. Now we need to apply this fix to the other branches. It looks like there were adjustments to privileges, on Github's side.
For future reference see - https://github.com/orgs/community/discussions/156181
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2743909884
@MuhammadTahaNaveed **PG17_prepare** has been renamed to **PG17** and I created a Docker Hub **PG17** build.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jirutka (via GitHub)" <gi...@apache.org>.
jirutka commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2642610638
And for Alpine Linux package 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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "thomastthai (via GitHub)" <gi...@apache.org>.
thomastthai commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2644729478
@jrgemignani, thank you for shedding additional light on the matter. Some issues can take a lot of time and resources to resolve. I appreciate the volunteer effort.
Clarity is a gift and perception can be people's reality. If a summary of what you typed above was shared and pinned months ago to add context, people would feel sympathy or empathy for what's happening versus wondering, "Is this project dead?" That's a fair ask, IMHO.
My email was forwarded to Jeff. He said he'll reply tomorrow.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2643601966
@knutole The core team wasn't made redundant at Bitnine/AGEDB, they eliminated the **entire** core team of developers. This has changed the priorities of many of the core developers, as most can understand.
Additionally, there are ongoing Apache and Apache AGE PMC issues with Bitnine/AGEDB that I can't go into here.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2643704714
I should note that there will need to be initial PRs to adjust the CI and build environment for **PG17_prepare**. So, it may be a week before this branch is ready to take PRs. Well, before additonal PRs will build properly.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "thomastthai (via GitHub)" <gi...@apache.org>.
thomastthai commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2644526509
@knutole, thanks for the minutes from the committee. I went to the same link you shared previously and got mostly a blank page with a link and button. The link led to ASF's minutes, not the AGE committee's.
<img width="381" alt="Image" src="https://github.com/user-attachments/assets/513b6ec1-0ed6-45ff-aaba-1af3cedf8d47" />
Good to know ASF and AGEDB worked things out.
~12 PMC members having write access. With the staleness of responses to PRs and Issues for the project in the last ~6 months, one wonders about the engagement and/or effectiveness of AGE PMC members.
It's reasonable for ASF to want control over the quality of the project. If the committee is the bottleneck, changes are needed to rectify the situation.
It sucks all the core members were let go. I hope they are doing ok. It'll be nice to have them back, but they have more pressing matters to deal with. Even without them, the lack of activities from most of the PMC members is curious. Thankfully, @jrgemignani is active. It's a lot of work for one person though.
I'm curious how involved Jeff Jirsa, AGE Committee Chair, has been since their appointment in July 2024.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "thomastthai (via GitHub)" <gi...@apache.org>.
thomastthai commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2642291371
@knutole, @jrgemignani's statement was clear. The team paid to work on AGE was let go — most likely because funding ran out or shifted to other priorities. Whatever the reason, he summarized the future direction below:
> Currently, there isn't an eta for, nor a roadmap to, an Apache AGE version for PG17 **or any continuing support**.
Paid work for an open source can accelerate a project until the money, passion, or time runs out. It sucks, as AGE is one of the more exciting projects for PostgreSQL.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "xeroxnir (via GitHub)" <gi...@apache.org>.
xeroxnir commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-3351098170
Any chance https://github.com/apache/age-viewer/ is fixed? The explorer tool is not working at all.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2353698629
@JamesInform Right now, PG 17 isn't in our roadmap. This could change in the future, but due to current resources, it is considered lower priority.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2441903180
@JamesInform @df7cb Currently, there isn't an eta for, nor a roadmap to, an Apache AGE version for PG17 or any continuing support. The core R&D team that was driving Apache AGE (paid to work on this project) was eliminated earlier this month.
This means that future features, updates, bug fixes, etc. will be at a lot slower pace, if at all. Unfortunately, I cannot coerce or hold volunteers to any particular schedule.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jamestiotio-oss (via GitHub)" <gi...@apache.org>.
jamestiotio-oss commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2667998226
Just commenting to prevent closure of the issue since it is one that I am also tracking!
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "MuhammadTahaNaveed (via GitHub)" <gi...@apache.org>.
MuhammadTahaNaveed commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2737658511
> @MuhammadTahaNaveed Does **PG17_prepare** look good to be renamed to **PG17**? Thoughts?
@jrgemignani Yes, we are good to go imo. The remaining work will be handled once the branch is renamed.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "knutole (via GitHub)" <gi...@apache.org>.
knutole commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2633017303
@jrgemignani What is happening with this project? It would be good to get some proper information about your statement "The core R&D team that was driving Apache AGE (paid to work on this project) was eliminated earlier this month."
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2643762649
@knutole Any Apache committer can submit a PR for review. Only PMC members can approve it, and not the submitter of said PR. Basic controls to protect the Apache AGE repository's integrity.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "jrgemignani (via GitHub)" <gi...@apache.org>.
jrgemignani commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2643823034
@knutole I'm copying/pasting this from the Apache AGE Chair -
> - asf projects grant committer status to individual who have established trust and merit as judged by the PMC
> - we don’t grant write access to companies just because they happen to be building a product based on the project
> - if the PMC determines that individuals - regardless of company - exhibit ability and trustworthiness, the PMC can and should invite them into the project
> - but everyone is a volunteer, so best effort and no promises of timelines
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "knutole (via GitHub)" <gi...@apache.org>.
knutole commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2643725499
> [@knutole](https://github.com/knutole) The core team wasn't made redundant at Bitnine/AGEDB, they eliminated the **entire** core team of developers. This has changed the priorities of many of the core developers, as most can understand.
>
> Additionally, there are ongoing Apache and Apache AGE PMC issues with Bitnine/AGEDB that I can't go into here.
I don't really understand, who are "they" in "they eliminated"? And what's the difference between "core team was made redundant at Bitnine/AGEDB" and "eliminated entire core team"?
All the while @uhayat, who apparently works at Bitnine, [laments](https://github.com/bitnine-oss/agensgraph/issues/663#issuecomment-2642724649) not having write access. It's all a bit confusing tbh.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "knutole (via GitHub)" <gi...@apache.org>.
knutole commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2643708548
@jrgemignani Do you know who and how many people currently have write access?
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "nicholasveloso (via GitHub)" <gi...@apache.org>.
nicholasveloso commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-2645861568
Sincerely, I hope the problems will be sorted out sooner rather than later, and that the project continues.
At our startup we had reached an agreement to use AGE as the graph database of choice to use for our products, just a couple days before it was posted that the core developer meant team had been dismissed and the project would have no active development for the foreseeable future.
Since then we kind of froze our work towards graph database implementations, because without any certainty fo the Apache AGE project would continue and after analyzing the other solutions, we concluded that ifwe go for something like Neo4j or AWS Neptune, which have very steep costs, our company would not be able shoulder th costs without a good revenue stream for it.
We are still probing if our current clients would be willing to agree to an increase of price on their current contracts for the additional capabilities. Specialy since thr need for Graph DBs was identified based on their suggestions and requests for new functionalities of current products.
If they aren't willing absorb the cost, it would be hard to get it going with a non open source solution, so AGE was practically our only choice, but if the amount of time without active development goes on, it would be ever harder to use AGE as time passes, as the landscape of solutions in need for Graph DBs widens and get ever more sofisticated.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] PostgreSQL 17 not supported [age]
Posted by "MuhammadTahaNaveed (via GitHub)" <gi...@apache.org>.
MuhammadTahaNaveed commented on issue #2111:
URL: https://github.com/apache/age/issues/2111#issuecomment-3353242816
> Any chance https://github.com/apache/age-viewer/ is fixed? The explorer tool is not running (npm issues/old dependencies/etc).
@xeroxnir @jrgemignani I will try to look into it. Since it hasn’t been maintained for a while and I haven’t worked on it before, it may take some time.
--
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: dev-unsubscribe@age.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org