Re: [HACKERS] Thanks for the TAP framework

Hello. For me Testgres https://github.com/postgrespro/testgres much better because I have the allergy for Perl. Unfortunately, it's not inside Postgres... 2017-03-20 10:21 GMT+03:00 Craig Ringer : > Hi > > It just occurred to me that much of what I've been doing recently > would've been exceedin

Re: [HACKERS] WIP: About CMake v2

2017-02-12 20:55 GMT+03:00 Vladimir Rusinov : > Overall, when things go wrong debugging cmake requires cmake knowledge, > while autotools mostly require shell knowledge which is much more common > (again, for sysadmins/packagers). It's not really true because of CMake scripts much easier than to

Re: [HACKERS] WIP: About CMake v2

2017-01-28 1:50 GMT+03:00 Michael Paquier : > On Fri, Jan 27, 2017 at 11:09 PM, Peter Eisentraut > wrote: > > On 1/24/17 8:37 AM, Tom Lane wrote: > >> Craig Ringer writes: > >>> Personally I think we should aim to have this in as a non default build > >>> mode in pg10 if it can be made ready, an

Re: [HACKERS] WIP: About CMake v2

e sends to compiler right place for uuid.h (I mean -I/usr/include and etc for gcc). > Yeah, I think this is how the MSVC stuff effectively works right now as > well. I glad to hear it. 2017-01-03 17:11 GMT+03:00 Peter Eisentraut < peter.eisentr...@2ndquadrant.com>: > On 12/30/16

[HACKERS] Small fix in pg_rewind (redundant declaration)

h. Thanks. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Some questions about the array.

. New patch in attach. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Companydiff --git a/doc/src/sgml/array.sgml b/doc/src/sgml/array.sgml index 4385a09..6ee71a5 100644 --- a/doc/src/sgml/array.sgml +++ b/doc/src/sgml/array.sgml @@ -257,6 +257,26 @@ SELECT

Re: [HACKERS] Some questions about the array.

omfortable behavior. Creating a separate array types in the form extension is very difficult IMHO. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] Some questions about the array.

nd error when omitted lower bound in INSERT like this: INSERT INTO arrtest_s (a[:2], b[1:2]) VALUES ('{1,2,3,4,5}', '{7,8,9}'); I fix it in new patch. Lower bound for new array is 1 by default. Thanks. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Ru

Re: [HACKERS] Some questions about the array.

On Tuesday 01 December 2015 15:30:47 Teodor Sigaev wrote: > As I understand, update should fail with any array, so, first update should > fail too. Am I right? You right. Done. New patch in attach. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Po

Re: [HACKERS] Some questions about the array.

On Monday 30 November 2015 08:58:49 you wrote: > +1 IMO this line of thinking is a dead end. Better handled via > functions, not syntax Maybe then add array_pyslice(start, end) when start is 0 and with negative indexes? Only for 1D array. What do you think? -- YUriy Zhuravlev Po

Re: [HACKERS] Some questions about the array.

cases error message should be the same or close. Done. Skipping lower boundary is no longer an error. Thank you for your review. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Companydiff --git a/doc/src/sgml/array.sgml b/doc/src/sgml/array.sgml in

Re: [HACKERS] WIP: About CMake v2

CMake most fixes modules like FindBISON and etc. This different philosophy. Thanks. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscri

Re: [HACKERS] WIP: About CMake v2

On Thursday 26 November 2015 17:42:16 you wrote: > No point in doing any work if you don't agree with the basic prerequisites. I meant that support for older versions of CMake I'll do when will implement other functions. -- YUriy Zhuravlev Postgres Professional: http://www.postgr

Re: [HACKERS] WIP: About CMake v2

CMake. On the one hand it is good that the GNU Make a stable and have not changed, but it can not last forever. It is possible to make support for CMake 2.6 but now is not the time when you have to think about it. I'll come back to this when all the functionality will work. Thanks.

Re: [HACKERS] WIP: About CMake v2

e more thing: a normal documentation came with 3.0. :) But I try to check my code for 2.8.11, now I have 3.4.0 (latest for Gentoo). Thanks. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@pos

Re: [HACKERS] WIP: About CMake v2

that make them > work anywhere but where the author wanted/needed. Now everything is much better. And it is worth split "make" and configuration. CMake better GNU Make and is similar to the m4 for configuring. But M4 older and elaborated. These are my feelings on the current work.

Re: [HACKERS] WIP: About CMake v2

help: https://github.com/stalkerg/postgres_cmake Thanks. PS All define for pg_config.h generate and testing truly -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make

Re: [HACKERS] Some questions about the array.

On Wednesday 11 November 2015 17:29:31 you wrote: > In this case the syntax is major issue. Any language should not to have any > possible feature on the world. I am about omitted boundaries. It almost does not change the syntax and with nothing conflicts. Thanks. -- YUriy Zhuravlev Po

Re: [HACKERS] Some questions about the array.

} it seems optional. Thanks. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Some questions about the array.

orner use cases. > > Regards > > Pavel Ok we can use {:} instead [:] for zero array access. The function is the solution half. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hack

Re: [HACKERS] Some questions about the array.

On Monday 09 November 2015 04:33:28 you wrote: > You can write it as a separate function instead of changing current syntax. I do not think, because we have a multi-dimensional arrays. And why we have [:] syntax now? -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russ

Re: [HACKERS] Some questions about the array.

ent. Of course it is possible and without it, but why? Thanks. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Some questions about the array.

nks. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Some questions about the array.

array which always starts with 0. Then we can use negative indexes, and you can always find the beginning of the array. Example: we have array [-3:3]={1,2,3,4,5,6,7} array[~0] == 1 array[~-1] == 7 array[~2:~-2] == {3,4,5,6} What do you think? -- YUriy Zhuravlev Postgres Professional: http://www.

Re: [HACKERS] Some questions about the array.

On Thursday 05 November 2015 23:45:53 you wrote: > On Thu, Nov 5, 2015 at 9:57 AM, YUriy Zhuravlev > > wrote: > > Hello hackers. > > There are comments to my patch? Maybe I should create a separate thread? > > Thanks. > > You should add this on commitfest.post

Re: [HACKERS] Some questions about the array.

On Thursday 05 November 2015 22:33:37 you wrote: > Would something like array[1:~1] as a syntax be acceptable to denote > backward counting? Very interesting idea! I could implement it. I just need to check for side effects. -- YUriy Zhuravlev Postgres Professional: http://www.postgresp

Re: [HACKERS] Some questions about the array.

Hello hackers. There are comments to my patch? Maybe I should create a separate thread? Thanks. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] clearing opfuncid vs. parallel query

ss suited for such development. Also at the moment Python is more common: http://www.tiobe.com/index.php/content/paperinfo/tpci/index.html -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsq

Re: [HACKERS] clearing opfuncid vs. parallel query

On Thursday 22 October 2015 09:26:46 David Fetter wrote: > On Thu, Oct 22, 2015 at 07:15:35PM +0300, YUriy Zhuravlev wrote: > > Hello. > > Currently using nodeToString and stringToNode you can not pass a > > full plan. In this regard, what is the plan to fix it? Or in the &g

Re: [HACKERS] clearing opfuncid vs. parallel query

helped to simplify the saved of query plans in the Postgres table. Thanks. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.p

Re: [HACKERS] clearing opfuncid vs. parallel query

e much more difficult. But my current generator just use the structure from the header files (by pycparser). Thanks. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make chan

Re: [HACKERS] clearing opfuncid vs. parallel query

On Thursday 22 October 2015 12:53:49 you wrote: > On Thu, Oct 22, 2015 at 12:15 PM, YUriy Zhuravlev > > wrote: > > Hello. > > Currently using nodeToString and stringToNode you can not pass a full > > plan. In this regard, what is the plan to fix it? Or in the under t

Re: [HACKERS] clearing opfuncid vs. parallel query

tree walker, I have an inner development. I am using python analyzing header files and generates a universal walker (parser, paths ,executer and etc trees), as well as the serializer and deserializer to jsonb. Maybe I should publish this code? Thanks. -- YUriy Zhuravlev Postgres Profess

Re: [HACKERS] Some questions about the array.

Hello again. I attached simple patch for omitted boundaries in the slice. This will simplify the writing of SQL. Instead: select arr[2:array_upper(arr, 1)]; you can write: select arr[2:]; simple and elegant. Omitted boundaries is prohibited in UPDATE. Thanks. -- YUriy Zhuravlev Postgres

[HACKERS] Some questions about the array.

something can be improved? P.S. I would like List datatype as in Python. Is there any fundamental objections? Or we just did not have the time and enthusiasm before? The current implementation I would call vectors or matrices but not arrays. IMHO -- YUriy Zhuravlev Postgres Professional: http

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

about Trac? http://trac.edgewall.org/wiki/TracUsers -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

a green field project are in operation here. Now any stick will help. IMHO -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.p

Re: [HACKERS] No Issue Tracker - Say it Ain't So!

k. > > Why not just use Github issues? I will also vote for github. We have github mirror now. In a pinch, you can use gitlab. PS mail lists outdated IMHO. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers maili

Re: [HACKERS] Move PinBuffer and UnpinBuffer to atomics

ght work. We will be tested. >your workload Simple pgbench -S for NUMA. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www

Re: [HACKERS] Move PinBuffer and UnpinBuffer to atomics

u're posting >things for review and you seem completely unwilling to actually respond >to points raised. I think we're just talking about different things. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers

Re: [HACKERS] Move PinBuffer and UnpinBuffer to atomics

wait. > Just for fun, what's the results if you use -M prepared ? Unfortunately now we can not check. :( -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To ma

Re: [HACKERS] Move PinBuffer and UnpinBuffer to atomics

tate not actual. In this embodiment, there is no significant difference between the two patches. For honest work will need used the CAS for all IF statement. Thanks! Hope for understanding. ^_^ -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company --

Re: [HACKERS] Scaling PostgreSQL at multicore Power8

ad: http://www.postgresql.org/message-id/2400449.GjM57CE0Yg@dinodell ? In our view it is correct, although this is not obvious. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [HACKERS] Move PinBuffer and UnpinBuffer to atomics

d comment before LockBufHdr(bufHdr) in SyncOneBuffer. We checked all functions with refcount and usage_count. Thanks! ^_^ -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.o

Re: [HACKERS] Move PinBuffer and UnpinBuffer to atomics

On Friday 11 September 2015 18:37:00 you wrote: > so unless I'm missing something, no, we haven't lost the lock. This section is protected by like LWLockAcquire(newPartitionLock, LW_EXCLUSIVE); before it (and we can't get this buffer from hash table). -- YUriy Zhuravlev Pos

Re: [HACKERS] Move PinBuffer and UnpinBuffer to atomics

re, in essence, nothing has changed. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] Move PinBuffer and UnpinBuffer to atomics

etails here: https://gist.github.com/stalkerg/773a81b79a27b4d5d63f Thank you. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Companydiff --git a/contrib/pg_buffercache/pg_buffercache_pages.c b/contrib/pg_buffercache/pg_buffercache_pages.c index 6622d22

[HACKERS] Fix small bug for build without HAVE_SYMLINK

Hello hackers. During my work on CMake I stumbled upon this simple bug. I think this is important for mingw users. The function is trying to return a variable that has not been announced. Patch in attach. Probably relevant for stable releases. Thanks! -- YUriy Zhuravlev Postgres Professional

Re: [HACKERS] WIP: About CMake v2

tem would certainly > require maintenance *every* time we touch the Makefiles. I can support the cmake build a separate git branch on github. When we (and users) see that all is well then we will think when and how to change GNUMake to CMake. -- YUriy Zhuravlev Postgres Professional: http://www.pos

Re: [HACKERS] Scaling PostgreSQL at multicore Power8

ect query from pgbech is common task not for all but... -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Scaling PostgreSQL at multicore Power8

On Monday 31 August 2015 17:54:17 Tomas Vondra wrote: > So does this mean it's worth testing the patch on x86 > or not, in it's current state? Its realy intersting. But you need have true 64 cores without HT. (32 core +HT not have effect) -- YUriy Zhuravlev Postgres Pr

Re: [HACKERS] WIP: About CMake v2

Thanks all hackers. I have not heard of fundamental problems and continue its development. :) -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] Scaling PostgreSQL at multicore Power8

ilence the compiler. This patch is concept only. -- YUriy Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] Scaling PostgreSQL at multicore Power8

NUMA nodes with 256 "CPUs"). To scale Postgres for large NUMA machine must be ported to the atomic operations bufmgr. During our tests, we no found errors in our patch, but most likely it is not true and this patch only for test. Who has any thoughts? -- YUriy Zhuravlev Postgres Pr

Re: [HACKERS] WIP: About CMake v2

ight. > > If the results represent little improvement, there will be little or no > appetite to jump through the dependency hoops needed to get the change > accepted. > > On the other hand, if there are big gains, that encourages pushing thru the > dependency issues. > &

[HACKERS] WIP: About CMake v2

Hello Hackers How would you react if I provided a patch which introduces a CMake build system? Old thread: http://www.postgresql.org/message-id/200812291325.13354.pete...@gmx.net The main argument against the "it's too hard". I'm right? Thanks! -- YUriy Zhuravlev Postgre