| From: | Jaime Soler <jaime(dot)soler(at)gmail(dot)com> |
|---|---|
| To: | "Eric J(dot) Van der Velden" <ericjvandervelden(at)gmail(dot)com> |
| Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Unrecognized parameter: max_prepared_foreign_transactions |
| Date: | 2019-04-03 13:46:41 |
| Message-ID: | CAKVUGgRCiz+am43KC_7aUwNV6FajvERMHwsqo4F_6fCWMDz4Hg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
I think that patch hasn't been commited yet:
https://commitfest.postgresql.org/21/1574/
El jue., 28 mar. 2019 a las 20:37, Eric J. Van der Velden (<
ericjvandervelden(at)gmail(dot)com>) escribió:
> On https://wiki.postgresql.org/wiki/2PC_on_FDW it says I have to set the
> configuration parameter "max_prepared_foreign_transactions" in
> postgresql.conf. When I restart postgres, I see:
>
> LOG: unrecognized configuration parameter
> "max_prepared_foreign_transactions" in file
> "/var/lib/postgresql/data/postgresql.conf" line 689
>
> Thanks,
> Eric.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2019-04-06 07:59:13 | ResultSet.getObject(..., LocalTime.class) not working with Postgres timetz type |
| Previous Message | kazachka | 2019-04-01 00:23:18 | [pgjdbc/pgjdbc] 5e48c4: style: remove extra empty lines (#1452) |