Shinya Kato

I am also having the same problem. I want to build postgres-operator-upgrade, but I can't find the Dockerfile for it.

> Hey Alex, maybe something like [that](https://www.cybertec-postgresql.com/wp-content/uploads/2021/02/Patroni-Logo.png) ? I would like to use this logo in my presentation. Do you have a trademark policy?

@Agalin >Looks like it's finally there. Today's commit to postgres-operator repo adds upgrade logic. Are you referring to [this commit](https://github.com/CrunchyData/postgres-operator/commit/0569dfcee312c8cecbe1c5cbd38d500d21699208)? I don't think this commit provides a Dockerfile to build...

This PR is not updated, so I rebased and create new PR https://github.com/apache/age/pull/1976.

The following comments are written before those tests, so I think no additional comments will be necessary. ``` -- cypher() function takes only a dollar-quoted string constant as an argument....

@devrimgunduz We released pg_bulkload 3.1.22 which is compatible with PostgreSQL 17. https://github.com/ossc-db/pg_bulkload/releases/tag/VERSION3_1_22 Give it a try!

Could you please tell me how to install and what is the directory structure?

Is there a path to pg_config? If not, you can run 1. `make USE_PGXS=1 PG_CONFIG=/path/to/pg_config` 2. `make USE_PGXS=1 PG_CONFIG=/path/to/pg_config install` 3. `make USE_PGXS=1 PG_CONFIG=/path/to/pg_config installcheck`

@jrgemignani @rafsun42 Sorry. Until v14, it seems to warn only when PostgreSQL starts. Warnings in SET statements are implemented in [this commit](https://github.com/postgres/postgres/commit/75d22069e00d638d08c04e3aba71688f3fb002ed). Therefore, the regression test has been removed.

I used the "OpenAPI (Swagger) Editor," which is a VS Code extension. Also, we can see the same errors on https://editor.swagger.io/. Since the file name is `openapi_spec.yml`, I think that...