John Gemignani

@rafsun42 Could this be rebased with the master and applied to the master branch instead of PG15? I'm not saying not to do PG15, just get it on the master...

@rafsun42 Additionally, it states that there are conflicts? 

@rafsun42 Interesting. It is still an issue in the latest master.

@rafsun42 We should make those changes so that these regression tests don't fail. Failing, but still okay, doesn't give warm fuzzies.

@saygoodbyye What are you trying to upgrade and from what version(s)? In general, upgrades of AGE are within a specific version of PostgreSQL between different versions of AGE. They are...

@saygoodbyye AGE for PostgreSQL version X does not run on PostgreSQL version Y. This is why we have different builds of AGE for each version of PostgreSQL. Additionally, we don't...

@saygoodbyye > As documentation says "pg_upgrade allows data stored in PostgreSQL data files to be upgraded to a later PostgreSQL major version without the data dump/restore typically required for major...

@saygoodbyye > Currently, we only support upgrades within a version of PG. However, we could add this as something to look into, resources permitting, in the future. Our priorities, atm,...

@ajit-satav Can you provide an output showing the two queries where one works and the other doesn't? Like what @rafsun42 showed above. Use the code option so that we can...

@ajit-satav Also, please explain what you mean by "start breaking". Do you mean taking a long time? When you query for variable length edges with just `[*]`, that means all...