Am 18.03.19 um 17:52 schrieb Adrian Klaver:
On 3/18/19 7:59 AM, Thomas Güttler wrote:
Am 18.03.19 um 15:49 schrieb Tom Lane:
Adrian Klaver writes:
On 3/18/19 7:33 AM, Thomas Güttler wrote:
If I used ascii data the tests took 52 seconds.
If I used random binary data the test took 250 sec
Sorry to revive this post, but I have the same problem:
I set a streaming replication slave with this steps:
1) create a physical replication slot in master
2) pg_basebackup -S slot (...)
3) create a recovery.conf with primary_conninfo, primary_slot_name and
recovery_min_apply_delay = '4d'
4) star
Yeah I'm not sure why you're looping using pointer math, the iterators are
there to provide that service. Another function to check out 'jsonb_each',
other than the set returning function parts, it does what it looks like
your are trying to do.
-Michel
On Mon, Mar 18, 2019 at 4:12 PM Andrew Gier
Hi All,
We're testing upgrade from postgres 10.6 to postgres 11.2 with pg_upgrade.
Before stopping pg10 we disabled subscription.
After upgrade and launching pg11, the existing logical replication
subscription is there and disabled.
stest=# \dRs+
List of s
I need this in my C code on the server side. Any link to the `jsonb_each`
for this? Examples I found in a quick search are on the client side in SQL.
I am just confused about the various jsonb types and how to effectively
extract values and convert between them:
There are Jsonb, JsonbValue (plus
jsonb_each is a wrapper around each_worker_jsonb. It produces a row for
every key/value pair in an object.
https://doxygen.postgresql.org/jsonfuncs_8c.html#a7511a3aa3918eb956f3f4211d07bdbb0
the iteration is:
while ((r = JsonbIteratorNext(&it, &v, skipNested)) != WJB_DONE)
On Tue, Mar 19, 2
On 2019-03-18 15:33:17 +0100, Thomas Güttler wrote:
> I did some benchmarking and in my setup there was major
> performance difference.
>
> I tested a ByteA column.
>
> If I used ascii data the tests took 52 seconds.
> If I used random binary data the test took 250 seconds.
>
> binary data is (r
Thanks a lot for the hint. I've used the iteration style and cleaned up the
code as far as I can.
It now correctly prints the keys and values, but the server crashes near
function return.
Any suggestions?
-- function code --
PG_FUNCTION_INFO_V1(print_kv_pair);
Datum
print_kv_pair(PG_FUNCTION_ARG
For server crashes you can't beat gdb in my opinion. It's a challenge but
worth it in the long run to have gdb skills if you're coding in C (or
Python, since pdb shares many of gdb's keybindings).
But just looking at the function I don't see what's immediately wrong,
what's your CREATE FUNCTION s
On Fri, Mar 15, 2019 at 4:46 PM Noah Misch wrote:
> Thanks. That rules out my guess. I don't have another guess at this time.
Even though I can't reproduce the problem myself, I'm quite keen to go
ahead and push the patch I proposed for v12 anyway, and close this
case. Otherwise this problem c
Thanks a lot. Fixing `CREATE FUNCTION` statement fixed the crash issue.
On Tue, Mar 19, 2019 at 3:18 PM Michel Pelletier
wrote:
> For server crashes you can't beat gdb in my opinion. It's a challenge but
> worth it in the long run to have gdb skills if you're coding in C (or
> Python, since pd
On 3/19/19 9:35 AM, Radoslav Nedyalkov wrote:
Hi All,
We're testing upgrade from postgres 10.6 to postgres 11.2 with pg_upgrade.
Before stopping pg10 we disabled subscription.
After upgrade and launching pg11, the existing logical replication
subscription is there and disabled.
stest=# \dRs+
BTW, my pointer math code was trying to mimic the below code I found for
"uniqueifyJsonbObject".
I just removed the logic for dropping duplicates. My difficulty is that I
couldn't find out how to interface the jsonb object I get from
my "print_kv_pair()" to this function. Just out of curiosity, I
Both 10.7 and 11.2 fail on FreeBSD 12-STABLE if --with-openssl is part
of the configure string.
The issue appears to be that FreeBSD updated OpenSSL to OpenSSL
1.1.1a-freebsd 20 Nov 2018 where the 11.x release of FreeBSD (and
previous was on 1.0.x -- e.g. OpenSSL 1.0.2o-freebsd 27 Mar 2018)
The
Thomas Munro writes:
> Even though I can't reproduce the problem myself, I'm quite keen to go
> ahead and push the patch I proposed for v12 anyway, and close this
> case. Otherwise this problem could just keep coming back until
> libldap.so is eventually entirely phased out by all distros. In 20
Karl Denninger writes:
> Both 10.7 and 11.2 fail on FreeBSD 12-STABLE if --with-openssl is part
> of the configure string.
Hmmm ... I don't have that exact configuration handy to try, but
we know that PG works against OpenSSL 1.1.1a in principle, and
it does work for me with FreeBSD 12.0-RC1 from
On Wed, Mar 20, 2019 at 11:13 AM Tom Lane wrote:
> Karl Denninger writes:
> > Both 10.7 and 11.2 fail on FreeBSD 12-STABLE if --with-openssl is part
> > of the configure string.
>
> Hmmm ... I don't have that exact configuration handy to try, but
> we know that PG works against OpenSSL 1.1.1a in
> "Karl" == Karl Denninger writes:
Karl> Both 10.7 and 11.2 fail on FreeBSD 12-STABLE if --with-openssl is
Karl> part of the configure string.
Nope, they work fine for me, running under 12-stable as of a couple of
weeks ago.
--
Andrew (irc:RhodiumToad)
On 3/19/2019 17:12, Tom Lane wrote:
> Karl Denninger writes:
>> Both 10.7 and 11.2 fail on FreeBSD 12-STABLE if --with-openssl is part
>> of the configure string.
> Hmmm ... I don't have that exact configuration handy to try, but
> we know that PG works against OpenSSL 1.1.1a in principle, and
>
On Wed, Mar 20, 2019 at 11:33 AM Karl Denninger wrote:
> Digging around I had the openssl-1.0.2r port on the system, which used to be
> necessary for some other stuff back before 12.x. I've removed it and it
> looks like that took care of it; for whatever reason configure was getting
> confuse
> "Karl" == Karl Denninger writes:
Karl> That was on a bare, new grab of the source from your repository and a
Karl> straight-up run of "./configure --with-openssl --with-perl", then
"gmake".
That's a configure line that has never worked on FreeBSD:
% ./configure --with-openssl --with-pe
On 3/19/2019 18:15, Andrew Gierth wrote:
>> "Karl" == Karl Denninger writes:
> Karl> That was on a bare, new grab of the source from your repository and a
> Karl> straight-up run of "./configure --with-openssl --with-perl", then
> "gmake".
>
> That's a configure line that has never worked
> "Karl" == Karl Denninger writes:
>> That's a configure line that has never worked on FreeBSD:
>>
>> % ./configure --with-openssl --with-perl
>> [...]
>> configure: error: readline header not found
>> If you have libedit already installed, see config.log for details on the
>> failure
On 3/19/2019 21:12, Andrew Gierth wrote:
>> "Karl" == Karl Denninger writes:
> >> That's a configure line that has never worked on FreeBSD:
> >>
> >> % ./configure --with-openssl --with-perl
> >> [...]
> >> configure: error: readline header not found
> >> If you have libedit already ins
> "Karl" == Karl Denninger writes:
Karl> "cc" on FreeBSD is now (and has been for quite some time) clang:
Karl> If it will compile Postgres now it definitely would not when it
Karl> was first shifted to;
People have been building PG with clang since at least as far back as
clang 3.1, and
On Wed, Mar 20, 2019 at 6:41 PM Andrew Gierth
wrote:
> ... (Though the fact that we prefer gcc to cc in
> configure if both are found is a decision that should probably be
> revisited, given that the reasons for that preference are mostly
> consigned to the graveyard of commercial Unix variants.)
26 matches
Mail list logo
