Hi
We are validating your request and according to the description, we assume that it is required for latest Ubuntu version.

Hi @lakshminarayana02, wow, thanks. Super quick.

Hmm, great question. I don't know enough about Ubuntu, but would it be safe to assume that "Ubuntu latest" would work with any version of PostgreSQL?

I suppose there might be a risk with providing a -v option for the version of PostgreSQL and then later running into issues because it can't run on whatever version of Ubuntu the runner is currently using.

What do you think?

Hi
acknowledged, we'll keep you updated.

Great, thanks @lakshminarayana02!

Hi
We tested it, and changes are likely to be implemented in forthcoming deployments based on the internal process. Please bear with us.

Hey @lakshminarayana02, super stuff. Thank you.!

Hi @PaulieScanlon - The requirement will be taken care under this announcement(#11723).
Thanks!

``

Thanks, @Prabhatkumar59. I've reviewed the update, and perhaps I'm not understanding correctly. My original request was to allow users to choose which version of Postgres to install, not to update the current version to 17.

E.g, this example uses the -v flag to install version 17.

jobs:
  dump-and-restore:
    runs-on: ubuntu-latest

    steps:
      - name: Start PostgreSQL Service
        run: |
          sudo systemctl start postgresql.service -v 17

Or, in this example it uses the -v flag to install version 14.

jobs:
  dump-and-restore:
    runs-on: ubuntu-latest

    steps:
      - name: Start PostgreSQL Service
        run: |
          sudo systemctl start postgresql.service -v 14

The idea is that users will be able to decide which version of Postgres the built-in service installs in the runner. Is that going to be possible with the next update?