Re: Postgres C-API: How to get the Oid for a custom type defined in a schema outside of the current search path

Hi, > Am 03.12.2020 um 11:01 schrieb Pavel Stehule : > > Hi > > čt 3. 12. 2020 v 10:32 odesílatel Michael Krüger > napsal: > Dear all, > > I need to find out the Oid of a custom type in C programming language. This > type is defined in a schema, outside of

Postgres C-API: How to get the Oid for a custom type defined in a schema outside of the current search path

Dear all, I need to find out the Oid of a custom type in C programming language. This type is defined in a schema, outside of the standard search path, e.g. public. I know that I can call TypenameGetTypid to find out an Oid. But this is not working for me if the type is not in the public namespa

Re: Parallel Query - Can it be used within functions?

- Function Scan on generic_query_python foo (cost=0.25..50.25 rows=5000 width=40) (actual time=49.920..49.922 rows=17 loops=1) Planning time: 0.029 ms Execution time: 49.977 ms (3 rows) Michael Krüger schrieb am F

Re: Parallel Query - Can it be used within functions?

actual time=49.920..49.922 rows=17 loops=1) > Buffers: shared hit=6388 > LOCATION: explain_ExecutorEnd, auto_explain.c:359 > QUERY PLAN > > ---

Re: Parallel Query - Can it be used within functions?

Dear all, still same behavior with Postgres 10.2 ... Just as a reminder that the issue still exists. Regards, Michael Andreas Kretschmer schrieb am Di., 6. Feb. 2018 um 08:35 Uhr: > Hi, > > > Am 06.02.2018 um 08:24 schrieb Michael Krüger: > > create or replace function rep

Parallel Query - Can it be used within functions?

Dear community, I need a bit of advice on parallel query execution. I have a table with roughly 2 million rows in it. These rows are distributed over a set of IDs. Therefore I can group my rows based on the ID set. If I query the table directly like this: select mediatrunkid,count(*)::numeric fr

Re: Slow alter sequence with PG10.1

Hello all, I think a good alternative was found and seems to be working fine. I really do appreciate all the help and feedback. Many thanks. Regards, Michael Adrian Klaver schrieb am Di., 23. Jan. 2018 um 02:12 Uhr: > On 01/22/2018 02:47 PM, Michael Krüger wrote: > > Hello all, >

Re: Slow alter sequence with PG10.1

new release of Postgres caused some severe headaches among our customers. If you all agree that this changed function should be equivalent to the original one, then its at least an easy fix. Thank you all for your fast responses. Regards, Michael Michael Krüger schrieb am Mo., 22. Jan. 2018 um 23:11

Re: Slow alter sequence with PG10.1

h the performance impact but more safety if needed. I will try if Adrians proposal does the trick for my application. Sounds promising, thanks. Regards, Michael Adrian Klaver schrieb am Mo., 22. Jan. 2018 um 22:29 Uhr: > On 01/22/2018 07:24 AM, Michael Krüger wrote: > > Dear community, >

Slow alter sequence with PG10.1

Dear community, I'm using PG10.1 on CentOS Linux release 7.4.1708 (Core) after upgrading it from PG9.6.6. My application heavily uses sequences and requires different increments of sequence numbers, e.g. a range of 100, 1000 or 5000 numbers, so it is not possible to set a fixed increment on a sequ