community.postgresql.postgresql_publication module – Add, update, or remove PostgreSQL publication
Note
This module is part of the community.postgresql collection (version 3.14.2).
You might already have this collection installed if you are using the ansible package.
It is not included in ansible-core.
To check whether it is installed, run ansible-galaxy collection list.
To install it, use: ansible-galaxy collection install community.postgresql.
You need further requirements to be able to use this module,
see Requirements for details.
To use it in a playbook, specify: community.postgresql.postgresql_publication.
Synopsis
- Add, update, or remove PostgreSQL publication. 
Requirements
The below requirements are needed on the host that executes this module.
- psycopg2 >= 2.5.1 
Parameters
| Parameter | Comments | 
|---|---|
| Specifies the name of a file containing SSL certificate authority (CA) certificate(s). If the file exists, the server’s certificate will be verified to be signed by one of these authorities. | |
| Drop publication dependencies. Has effect with state=absent only. Choices: 
 | |
| List of tables and its columns to add to the publication. If no columns are passed for table, it will be published as a whole. Mutually exclusive with tables and tables_in_schema. | |
| Sets a comment on the publication. To reset the comment, pass an empty string. | |
| Any additional parameters to be passed to libpg. These parameters take precedence. Default:  | |
| Name of the database to connect to and where the publication state will be changed. The  | |
| Host running the database. If you have connection issues when using  Default:  | |
| The password this module should use to establish its PostgreSQL session. Default:  | |
| Path to a Unix domain socket for local connections. Default:  | |
| The username this module should use to establish its PostgreSQL session. Default:  | |
| Name of the publication to add, update, or remove. | |
| Publication owner. If owner is not defined, the owner will be set as login_user or session_role. | |
| Dictionary with optional publication parameters. Available parameters depend on PostgreSQL version. | |
| Database port to connect to. Default:  | |
| Optional dictionary of row filters to apply to tables or columns of the publication. Mutually exclusive with tables_in_schema. | |
| Switch to session_role after connecting. The specified session_role must be a role that the current login_user is a member of. Permissions checking for SQL commands is carried out as though the session_role were the one that had logged in originally. | |
| Specifies the file name of the client SSL certificate. | |
| Specifies the location for the secret key used for the client certificate. | |
| Determines whether or with what priority a secure SSL TCP/IP connection will be negotiated with the server. See https://www.postgresql.org/docs/current/static/libpq-ssl.html for more information on the modes. Default of  Choices: 
 | |
| The publication state. Choices: 
 | |
| List of tables to add to the publication. If no value is set all tables are targeted. If the publication already exists for specific tables and tables is not passed, nothing will be changed. If you need to add all tables to the publication with the same name, drop existent and create new without passing tables. Mutually exclusive with tables_in_schema and columns. | |
| Specifies a list of schemas to add to the publication to replicate changes for all tables in those schemas. If you want to remove all schemas, explicitly pass an empty list  Supported since PostgreSQL 15. Mutually exclusive with tables and columns. | |
| If  It makes sense to use  Choices: 
 | 
Attributes
| Attribute | Support | Description | 
|---|---|---|
| Support: full | Can run in check_mode and return changed status prediction without modifying target. | 
Notes
Note
- PostgreSQL version must be 10 or greater. 
- The default authentication assumes that you are either logging in as or sudo’ing to the - postgresaccount on the host.
- To avoid “Peer authentication failed for user postgres” error, use postgres user as a become_user. 
- This module uses - psycopg, a Python PostgreSQL database adapter. You must ensure that- psycopg2 >= 2.5.1or- psycopg3 >= 3.1.8is installed on the host before using this module.
- If the remote host is the PostgreSQL server (which is the default case), then PostgreSQL must also be installed on the remote host. 
- For Ubuntu-based systems, install the - postgresql,- libpq-dev, and- python3-psycopg2packages on the remote host before using this module.
See Also
See also
- CREATE PUBLICATION reference
- Complete reference of the CREATE PUBLICATION command documentation. 
- ALTER PUBLICATION reference
- Complete reference of the ALTER PUBLICATION command documentation. 
- DROP PUBLICATION reference
- Complete reference of the DROP PUBLICATION command documentation. 
Examples
- name: Create a new publication with name "acme" targeting all tables in database "test"
  community.postgresql.postgresql_publication:
    login_db: test
    name: acme
    comment: Made by Ansible
- name: Create publication "acme" publishing only prices and vehicles tables
  community.postgresql.postgresql_publication:
    name: acme
    tables:
    - prices
    - vehicles
- name: Create publication "acme" publishing only prices table and id and name from vehicles tables
  community.postgresql.postgresql_publication:
    name: acme
    columns:
      prices:
      vehicles:
        - id
        - name
- name: Create publication "acme" publishing id and name from vehicles tables, with a row filter
  community.postgresql.postgresql_publication:
    name: acme
    columns:
      vehicles:
        - id
        - name
    rowfilters:
        vehicles: (id > 100)
- name: >
    Assuming publication "acme" exists, publishing id and name from vehicles table with a
    row filter (id > 100), remove and re-add the table to the publication, with the updated row filter
  community.postgresql.postgresql_publication:
    name: acme
    columns:
      vehicles:
        - id
        - name
    rowfilters:
        vehicles: WHERE (id > 100) AND (id < 200)
- name: Create a new publication "acme" for tables in schema "myschema"
  community.postgresql.postgresql_publication:
    login_db: test
    name: acme
    tables_in_schema: myschema
- name: Remove all schemas from "acme" publication
  community.postgresql.postgresql_publication:
    login_db: test
    name: acme
    tables_in_schema: []
- name: >
    Create publication "acme", set user alice as an owner, targeting all tables
    Allowable DML operations are INSERT and UPDATE only
  community.postgresql.postgresql_publication:
    name: acme
    owner: alice
    parameters:
      publish: 'insert,update'
- name: >
    Assuming publication "acme" exists and there are targeted
    tables "prices" and "vehicles", add table "stores" to the publication
  community.postgresql.postgresql_publication:
    name: acme
    tables:
    - prices
    - vehicles
    - stores
- name: Remove publication "acme" if exists in database "test"
  community.postgresql.postgresql_publication:
    login_db: test
    name: acme
    state: absent
Return Values
Common return values are documented here, the following are the fields unique to this module:
| Key | Description | 
|---|---|
| Flag indicates that all tables are published. Returned: if publication exists Sample:  | |
| Flag indicates the publication exists or not at the end of runtime. Returned: success Sample:  | |
| Owner of the publication at the end of runtime. Returned: if publication exists Sample:  | |
| Publication parameters at the end of runtime. Returned: if publication exists Sample:  | |
| List of executed queries. Returned: success Sample:  | |
| List of tables in the publication at the end of runtime. If all tables are published, returns empty list. Returned: if publication exists Sample:  | 
