On Fri, Mar 18, 2022 at 06:15:47PM +1300, Thomas Munro wrote:
>
> No idea what's happening here but one observation is that that animal
> is running an older distro that shipped with ICU 5.0. Commit b8f9a2a6
> may hold a clue...
Right. I'm setting up a similar podman environment, hopefully more
On Fri, Mar 18, 2022 at 12:45 AM Tomas Vondra
wrote:
>
> Hmm, this seems to have failed on wrasse [1], due to a timeout when
> waiting for tablesync to complete:
>
> 2022-03-17 17:39:28.247 CET [19962:1] LOG: logical replication table
> synchronization worker for subscription "sub2", table "tab1"
Add circular WAL decoding buffer, take II.
Teach xlogreader.c to decode the WAL into a circular buffer. This will
support optimizations based on looking ahead, to follow in a later
commit.
* XLogReadRecord() works as before, decoding records one by one, and
allowing them to be examined via t
On Fri, Mar 18, 2022 at 4:12 PM Julien Rouhaud wrote:
> On Fri, Mar 18, 2022 at 11:01:11AM +0900, Michael Paquier wrote:
> > FYI, prion is complaining here:
> > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2022-03-18%2001%3A43%3A13
> >
> > Some details:
> > # Failed test 'fai
Hi,
On Fri, Mar 18, 2022 at 11:01:11AM +0900, Michael Paquier wrote:
>
> FYI, prion is complaining here:
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=prion&dt=2022-03-18%2001%3A43%3A13
>
> Some details:
> # Failed test 'fails for invalid ICU locale: matches'
> # at t/001_initdb.p
Hi Peter,
On Thu, Mar 17, 2022 at 10:22:32AM +, Peter Eisentraut wrote:
> Add option to use ICU as global locale provider
>
> This adds the option to use ICU as the default locale provider for
> either the whole cluster or a database. New options for initdb,
> createdb, and CREATE DATABASE a
Fix header inclusion order in pg_receivewal.c
lz4frame.h was getting declared after the headers specific to Postgres,
but it needs to be included between postgres_fe.h and the internal
headers.
Issue introduced by ba5.
Reported-by: Justin Prysby
Discussion: https://postgr.es/m/20220317111220
Declare aarch64 has single copy atomicity for 8 byte values.
Architecture Reference Manual for ARMv8 B2.2.1 [1]
For explicit memory effects generated from an Exception level the
following rules apply:
- A read that is generated by a load instruction that loads a single
general-purpose register an
Don't bother to attach column name lists to RowExprs of named types.
If a RowExpr is marked as returning a named composite type, we aren't
going to consult its colnames list; we'll use the attribute names
shown for the type in pg_attribute. Hence, skip storing that list,
to save a few nanoseconds
Revert applying column aliases to the output of whole-row Vars.
In commit bf7ca1587, I had the bright idea that we could make the
result of a whole-row Var (that is, foo.*) track any column aliases
that had been applied to the FROM entry the Var refers to. However,
that's not terribly logically c
Revert applying column aliases to the output of whole-row Vars.
In commit bf7ca1587, I had the bright idea that we could make the
result of a whole-row Var (that is, foo.*) track any column aliases
that had been applied to the FROM entry the Var refers to. However,
that's not terribly logically c
Revert applying column aliases to the output of whole-row Vars.
In commit bf7ca1587, I had the bright idea that we could make the
result of a whole-row Var (that is, foo.*) track any column aliases
that had been applied to the FROM entry the Var refers to. However,
that's not terribly logically c
Revert applying column aliases to the output of whole-row Vars.
In commit bf7ca1587, I had the bright idea that we could make the
result of a whole-row Var (that is, foo.*) track any column aliases
that had been applied to the FROM entry the Var refers to. However,
that's not terribly logically c
Revert applying column aliases to the output of whole-row Vars.
In commit bf7ca1587, I had the bright idea that we could make the
result of a whole-row Var (that is, foo.*) track any column aliases
that had been applied to the FROM entry the Var refers to. However,
that's not terribly logically c
Revert applying column aliases to the output of whole-row Vars.
In commit bf7ca1587, I had the bright idea that we could make the
result of a whole-row Var (that is, foo.*) track any column aliases
that had been applied to the FROM entry the Var refers to. However,
that's not terribly logically c
On 3/17/22 20:15, Tomas Vondra wrote:
> Hmm, this seems to have failed on wrasse [1], due to a timeout when
> waiting for tablesync to complete:
>
> 2022-03-17 17:39:28.247 CET [19962:1] LOG: logical replication table
> synchronization worker for subscription "sub2", table "tab1" has started
> 20
Hmm, this seems to have failed on wrasse [1], due to a timeout when
waiting for tablesync to complete:
2022-03-17 17:39:28.247 CET [19962:1] LOG: logical replication table
synchronization worker for subscription "sub2", table "tab1" has started
2022-03-17 17:39:28.258 CET [19964:1] LOG: logical
Refactor code for reading and writing relation map files.
Restructure things so that the functions which update the global
variables shared_map and local_map are separate from the functions
which just read and write relation map files without touching any
global variables.
In the new structure of
Fix row filters with multiple publications
When publishing changes through a artition root, we should use the row
filter for the top-most ancestor. The relation may be added to multiple
publications, using different ancestors, and 52e4f0cd47 handled this
incorrectly. With c91f71b9dc we find the co
On Tue, Mar 15, 2022 at 3:04 PM Andres Freund wrote:
> Seems like this ought to have at least some basic test to make sure it
> actually works / keeps working?
Wouldn't hurt, although it may be a little bit tricky to getting it
work portably. I'll try to take a look at it.
--
Robert Haas
EDB: h
doc: Add documentation for new field pg_database.daticulocale
forgotten in f2553d43060edb210b36c63187d52a632448e1d2
Author: Shinoda, Noriyoshi (PN Japan FSIP)
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/a9b7e92084cdea1bd397ec26c3233206932f29c7
Modified Files
Split ExecUpdate and ExecDelete into reusable pieces
Create subroutines ExecUpdatePrologue / ExecUpdateAct /
ExecUpdateEpilogue, and similar for ExecDelete.
Introduce a new struct to be used internally in nodeModifyTable.c,
dubbed ModifyTableContext, which contains all context information needed
Add option to use ICU as global locale provider
This adds the option to use ICU as the default locale provider for
either the whole cluster or a database. New options for initdb,
createdb, and CREATE DATABASE are used to select this.
Since some (legacy) code still uses the libc locale facilities
23 matches
Mail list logo
