Re: [DISCUSS] Apache AGE for Postgres 12 - Version

[Pieterjan De Potter]

Dear Everyone,

I too think it would be nice to have similar version numbering for 
similar feature sets.


One question that could make this impossible though: will there be 
future features that will only be implemented for some versions of 
Postgres (11, 12, 13, 14, 15, ...) because of underlying features 
supported by those particular Postgres versions? Or would that at that 
point be a reason to stop support for Postgres versions that don't 
support these underlying features?


Kind regards,
Pieterjan


On 29.09.22 21:23, Jasper Blues wrote:

I think it should be versioned after the main development/R&D version.

*Reasons: *
*
*

  * It is easy to tie back to what this version was based off, without
looking up an index (which could be prone to error).
  * If there is an as yet unfixed edge case bug affecting some portion
of users on a particular version+pgVersion, they may have some
confidence about what up/downgrade version to try should they also
want to up/downgrade Postgres.
  * Simplicity : It is one of the core XP values along with
communication, feedback, courage and respect. 




On Sep 30, 2022, at 5:18 AM, Eya Badal > wrote:


Dear Everyone,

We are planning on our first release of Apache AGE for Postgres 12. It 
will be based on the Apache AGE 1.1.0 release that supports Postgres 
11. There will be a prefix for this release and all Postgres 12 
supported releases.


However, since this is the first Postgres 12 release, should the 
version be 1.0.0 or 1.1.0 because it is based on the 1.1.0 release for 
Postgres 11?


Please share your thoughts and suggestions.

Thank you very much,
Eya

Re: [DISCUSS] Apache AGE for Postgres 12 - Version

[Muhammad Shoaib]

Hi Pertejan,

Currently this is not the case. However, in the future new versions might
have more features than older versions.

I'll support the following

   1. for PG 11, AGE_11_1.1.0
   2. for PG 12, AGE_12_1.1.0


Kind regards
Shoaib

On Fri, Sep 30, 2022 at 9:52 AM Pieterjan De Potter
 wrote:

> Dear Everyone,
>
> I too think it would be nice to have similar version numbering for
> similar feature sets.
>
> One question that could make this impossible though: will there be
> future features that will only be implemented for some versions of
> Postgres (11, 12, 13, 14, 15, ...) because of underlying features
> supported by those particular Postgres versions? Or would that at that
> point be a reason to stop support for Postgres versions that don't
> support these underlying features?
>
> Kind regards,
> Pieterjan
>
>
> On 29.09.22 21:23, Jasper Blues wrote:
> > I think it should be versioned after the main development/R&D version.
> >
> > *Reasons: *
> > *
> > *
> >
> >   * It is easy to tie back to what this version was based off, without
> > looking up an index (which could be prone to error).
> >   * If there is an as yet unfixed edge case bug affecting some portion
> > of users on a particular version+pgVersion, they may have some
> > confidence about what up/downgrade version to try should they also
> > want to up/downgrade Postgres.
> >   * Simplicity : It is one of the core XP values along with
> > communication, feedback, courage and respect.
> >
> >
> >
> >> On Sep 30, 2022, at 5:18 AM, Eya Badal  >> > wrote:
> >>
> >> Dear Everyone,
> >>
> >> We are planning on our first release of Apache AGE for Postgres 12. It
> >> will be based on the Apache AGE 1.1.0 release that supports Postgres
> >> 11. There will be a prefix for this release and all Postgres 12
> >> supported releases.
> >>
> >> However, since this is the first Postgres 12 release, should the
> >> version be 1.0.0 or 1.1.0 because it is based on the 1.1.0 release for
> >> Postgres 11?
> >>
> >> Please share your thoughts and suggestions.
> >>
> >> Thank you very much,
> >> Eya
> >
>
>

[GitHub] [age] mhmdawnallah commented on issue #290: Initial Research for Supporting GraphQL

[GitBox]

mhmdawnallah commented on issue #290:
URL: https://github.com/apache/age/issues/290#issuecomment-1263373402

   @JoshInnis Discord Invitation link is expired. Could you please re-update 
it? Thanks for your time and consideration


-- 
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-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [age] JoshInnis commented on issue #290: Initial Research for Supporting GraphQL

[GitBox]

JoshInnis commented on issue #290:
URL: https://github.com/apache/age/issues/290#issuecomment-1263593976

   https://discord.gg/VD4drHrh


-- 
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-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [age] JoshInnis commented on issue #271: Complete Graph

[GitBox]

JoshInnis commented on issue #271:
URL: https://github.com/apache/age/issues/271#issuecomment-1263797214

   ag_catalog.age_create_complete_graph(graph_name Name, nodes int)


-- 
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-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [age] jrgemignani opened a new issue, #313: Become familiar with the gdb debugger and PostgreSQL flow

[GitBox]

jrgemignani opened a new issue, #313:
URL: https://github.com/apache/age/issues/313

   This task is to help you become familiar with the GDB debugger and how a 
command is processed in PostgreSQL.
   
   GDB is a full featured debugger with lots of capabilities. But, for most 
tasks, you only need to know a few commands and a basic instruction of how to 
use it. The GDB documentation is available online and if you have any 
questions. You can also comment here or message us if you have any questions.
   
   To debug a PostgreSQL session  -
   
   1. You will need to make sure that when you configured and built PostgreSQL, 
you did so with any debugging flags enabled.
   2. PostgreSQL needs to be running.
   3. The PostgreSQL session that you want to debug needs to be open.
   4. Your GDB session needs to be in the **bin** directory for the PostgreSQL 
distribution that you are using.
   5. You need to know the process of the **session** that you will be 
debugging.
   6. You can then execute the command `gdb -tui postgres the_pid_number`
   7. You will need to set one, or more, breakpoints (b) and then tell GDB to 
continue (c)
   
   The basic GDB commands are -
   
   - **b** for breakpoint, fx, `b exec_simple_query` or `b 930` 
   - **c** for continue - continues to the next breakpoint
   - **n** for next line
   - **s** for step into
   - **p** for print, fx, `p *node` 
   - **d** for delete all breakpoints
   - **q** for quit
   
   A good breakpoint for the start of a PostgreSQL session is 
`exec_simple_query`. Unless you know of a specific area or function that you 
need to look at. For this task, `exec_simple_query` is a good start.
   
   In this task you will use the debugger to trace the `SELECT 1;` statement 
from beginning to end (output). You do **not** need to worry about the planner 
(you'll know it when you see it). You do **not** need to worry about the 
details, just the general flow. It is **not** expected that you will completely 
understand most of what you see. However, it will help you get used to the 
debugger and a bit of how PostgreSQL processes commands.
   
   An example, to get you started -
   
   
![Image](https://user-images.githubusercontent.com/1505136/193316271-f119e8b2-1249-4383-b485-63c20918e5d8.png)
   
   The session will look something like the following -
   
   
![Image](https://user-images.githubusercontent.com/1505136/193317211-68092f26-275e-407a-ab24-392b7edaf4b9.png)
   
   From there you would enter in a break point and tell it to continue -
   
![Image](https://user-images.githubusercontent.com/1505136/193317100-22f102cc-2ad4-46eb-97ad-d5aae22f51a2.png)
   
   From your session enter the command `SELECT 1;` which is a good, and 
relatively simple one, to follow -
   
   
![Image](https://user-images.githubusercontent.com/1505136/193318651-f6d48359-169d-4541-936c-3605b4bee308.png)
   
   The debugger session will then break at `exec_simple_query ` -
   
   
![Image](https://user-images.githubusercontent.com/1505136/193318491-f0357b2a-0f31-4f10-a09d-2f8e30346abb.png)
   
   


-- 
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-unsubscr...@age.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: [DISCUSS] Apache AGE for Postgres 12 - Version

[John Gemignani]

It is also likely, for a little while at least, that AGE 11 will have more
current features and fixes than 12 or successive versions.

We are definitely going to need to come up with a process to address
features and fixes being added in and propagated through the appropriate
versions.

john

On Fri, Sep 30, 2022 at 1:14 AM Muhammad Shoaib 
wrote:

> Hi Pertejan,
>
> Currently this is not the case. However, in the future new versions might
> have more features than older versions.
>
> I'll support the following
>
>1. for PG 11, AGE_11_1.1.0
>2. for PG 12, AGE_12_1.1.0
>
>
> Kind regards
> Shoaib
>
> On Fri, Sep 30, 2022 at 9:52 AM Pieterjan De Potter
>  wrote:
>
> > Dear Everyone,
> >
> > I too think it would be nice to have similar version numbering for
> > similar feature sets.
> >
> > One question that could make this impossible though: will there be
> > future features that will only be implemented for some versions of
> > Postgres (11, 12, 13, 14, 15, ...) because of underlying features
> > supported by those particular Postgres versions? Or would that at that
> > point be a reason to stop support for Postgres versions that don't
> > support these underlying features?
> >
> > Kind regards,
> > Pieterjan
> >
> >
> > On 29.09.22 21:23, Jasper Blues wrote:
> > > I think it should be versioned after the main development/R&D version.
> > >
> > > *Reasons: *
> > > *
> > > *
> > >
> > >   * It is easy to tie back to what this version was based off, without
> > > looking up an index (which could be prone to error).
> > >   * If there is an as yet unfixed edge case bug affecting some portion
> > > of users on a particular version+pgVersion, they may have some
> > > confidence about what up/downgrade version to try should they also
> > > want to up/downgrade Postgres.
> > >   * Simplicity : It is one of the core XP values along with
> > > communication, feedback, courage and respect.
> > >
> > >
> > >
> > >> On Sep 30, 2022, at 5:18 AM, Eya Badal  > >> > wrote:
> > >>
> > >> Dear Everyone,
> > >>
> > >> We are planning on our first release of Apache AGE for Postgres 12. It
> > >> will be based on the Apache AGE 1.1.0 release that supports Postgres
> > >> 11. There will be a prefix for this release and all Postgres 12
> > >> supported releases.
> > >>
> > >> However, since this is the first Postgres 12 release, should the
> > >> version be 1.0.0 or 1.1.0 because it is based on the 1.1.0 release for
> > >> Postgres 11?
> > >>
> > >> Please share your thoughts and suggestions.
> > >>
> > >> Thank you very much,
> > >> Eya
> > >
> >
> >
>

[GitHub] [age-website] arun-esh opened a new issue, #84: Improve the documentation for docker command line

[GitBox]

arun-esh opened a new issue, #84:
URL: https://github.com/apache/age-website/issues/84

   Apache AGE via docker: require some extra arguments to make it 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-unsubscr...@age.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [age-website] JoshInnis commented on issue #84: Improve the documentation for docker command line

[GitBox]

JoshInnis commented on issue #84:
URL: https://github.com/apache/age-website/issues/84#issuecomment-1264070093

   The docker command requires certain environmental variables to be added to 
work correctly:
   
   ```
   docker run \
   --name myPostgresDb  \
   -p 5455:5432 \
   -e POSTGRES_USER=postgresUser \
   -e POSTGRES_PASSWORD=postgresPW \
   -e POSTGRES_DB=postgresDB \
   -d \
   apache/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-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [age] Dzordzu closed issue #302: Using postgres variables within cypher function

[GitBox]

Dzordzu closed issue #302: Using postgres variables within cypher function
URL: https://github.com/apache/age/issues/302


-- 
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-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org