o implement this
feature?
Maybe in this thread[1] your described problem are solved through
introducing Parallel Append node?
1.
https://www.postgresql.org/message-id/CAJ3gD9dy0K_E8r727heqXoBmWZ83HwLFwdcaSSmBQ1%2BS%2BvRuUQ%40mail.gmail.com
--
Regards,
Maksim Milyutin
--
Sent via pg
x27;CREATE INDEX
paritioned_table' statement as a cascade operation.
As a result, we can specify name for each concrete index while
recreating a whole hierarchy.
--
Regards,
Maksim Milyutin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
esql.org/message-id/CAM-w4HOVftuv5RVi3a%2BsRV6nBpg204w7%3DL8MwPXVvYBFo1uM1Q%40mail.gmail.com
--
Regards,
Maksim Milyutin
ssion from composite type.
On November commitfest I'll lay out patch that covers your case.
--
Regards,
Maksim Milyutin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
'pair' type I'll get the following message:
ERROR: cached plan must not change result type
I don't know whether it's right behavior. Anyhow your point is a good
motivation to experiment and investigate different scenarios of work
with cached plan that depends on non-stable type. Thanks for that.
--
Regards,
Maksim Milyutin
On 26.09.2017 23:25, Maksim Milyutin wrote:
25.09.17 20:50, Maksim Milyutin wrote:
I have found out the problem when try to sequentially call the
function that casts constant to composite type of temporary table
that is deleted ateach transaction termination (i.e. at each function
call
er. Namely conflict in src/backend/executor/execMain.c
--
Regards,
Maksim Milyutin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
be missing something.
Anyhow, we have to protect ourselves from empty output from
*pg_get_partition_constraintdef*. And printing *No partition constraint*
would be good point to start to examine why we didn't get any constraint
definition.
--
Regards,
Maksim Milyutin
On 28.09.2017 16:29, Jesper Pedersen wrote:
On 09/28/2017 09:19 AM, Maksim Milyutin wrote:
E.g. "No partition constraint" vs. "Partition constraint:
satisfies_hash_partition(...)".
I also noticed ambiguity in printing "No partition constraint" in
non-verbose
erbose one for
partition tables regardless of the type of partition.
Attached small patch removes any output about partition constraint in
non-verbose mode.
--
Regards,
Maksim Milyutin
diff --git a/src/bin/psql/describe.c b/src/bin/psql/describe.c
index d22ec68..b301219 100644
--- a/src/bin/psq
25.09.17 20:50, Maksim Milyutin wrote:
I have found out the problem when try to sequentially call the
function that casts constant to composite type of temporary table that
is deleted ateach transaction termination (i.e. at each function call
completion).
For example, we have the following
On 19.09.2017 11:09, Daniel Gustafsson wrote:
Removing reviewer Maksim Milyutin from patch entry due to inactivity and
community account email bouncing. Maksim: if you are indeed reviewing this
patch, then please update the community account and re-add to the patch entry.
cheers ./daniel
nd is not invalidated at each function call. This is because** the
statement of this query doesn't have any dependency from the 'tbl'
relation (/relationOids/ list of /CachedPlanSource/ struct).
Attached patch resolves this problem by adding dependency from relation
upon detection
my
patch works
only with explain (and segfault without).
Instrumentation is initialized only with analyze (log_analyze is true)[1]
Is there a simple way to get ntuples?
It's interesting question. In one's time I didn't find any way to get
the amount of tuples emitted from a node.
1. contrib/auto_explain/auto_explain.c:221
--
Regards,
Maksim Milyutin
10.08.17 23:01, Robert Haas wrote:
On Wed, Apr 19, 2017 at 5:25 AM, Maksim Milyutin
wrote:
Ok, thanks for the feedback. Then I'll use a new relkind for local
partitioned index in further development.
Any update on this?
I'll continue to work soon. Sorry for so long delay.
On 19.04.2017 17:13, Remi Colinet wrote:
Maksim,
2017-04-18 20:31 GMT+02:00 Maksim Milyutin mailto:m.milyu...@postgrespro.ru>>:
On 18.04.2017 17:39, Remi Colinet wrote:
Regarding the queryDesc state of SQL query upon receiving a
request to
report its exe
On 19.04.2017 11:42, Ashutosh Bapat wrote:
On Tue, Apr 18, 2017 at 4:43 PM, Maksim Milyutin
wrote:
Local partitioned indexes can be recognized through the check on the relkind
of table to which the index refers. Something like this:
heap = relation_open(IndexGetRelation(indexid, false
]. I only manipulate runtime statistics (data in
the structure 'Instrumentation') to achieve the printing state of
running query.
1. https://www.postgresql.org/message-id/24182.1472745492%40sss.pgh.pa.us
2.
https://github.com/postgrespro/pg_query_state/blob/master/runtime_expl
robust PROGRESS command.
1. https://github.com/postgrespro/pg_query_state
2.
https://www.postgresql.org/message-id/dbfb1a42-ee58-88fd-8d77-550498f52bc5%40postgrespro.ru
3. https://www.postgresql.org/message-id/24182.1472745492%40sss.pgh.pa.us
--
Maksim Milyutin
Postgres Professional: ht
On 18.04.2017 13:08, Amit Langote wrote:
Hi,
Hi, Amit!
On 2017/04/17 23:00, Maksim Milyutin wrote:
Ok, thanks for the note.
But I want to discuss the relevancy of introduction of a new relkind for
partitioned index. I could to change the control flow in partitioned index
creation
On 10.04.2017 14:20, Robert Haas wrote:
On Tue, Apr 4, 2017 at 12:10 PM, Maksim Milyutin
wrote:
1. I have added a new relkind for local indexes named RELKIND_LOCAL_INDEX
(literal 'l').
Seems like it should maybe be RELKIND_PARTITIONED_INDEX. There's
nothing particularly "
On 10.04.2017 13:46, Greg Stark wrote:
On 4 April 2017 at 17:10, Maksim Milyutin wrote:
3. As I noticed early pg_depend table is used for cascade deleting indexes
on partitioned table and its children. I also use pg_depend to determine
relationship between parent and child indexes when
On 07.04.2017 13:05, Etsuro Fujita wrote:
On 2016/12/14 16:20, Etsuro Fujita wrote:
On 2016/12/09 19:46, Maksim Milyutin wrote:
I would like to work on two tasks:
- insert (and eventually update) tuple routing for foreign partition.
- the ability to create an index on the parent and have all
On 01.03.2017 13:53, Maksim Milyutin wrote:
Hi hackers!
As I've understood from thread [1] the main issue of creating local
indexes for partitions is supporting REINDEX and DROP INDEX operations
on parent partitioned tables. Furthermore Robert Haas mentioned the
problem of creating index o
rel->rd_rel->relkind != RELKIND_FOREIGN_TABLE &&
+ rel->rd_rel->relkind != RELKIND_PARTITIONED_TABLE)
{
RelationDropStorage(rel);
}
--
Maksim Milyutin
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
s lack
is caught through if-statement [1] I think it is not safe.
My patch fixes this issue.
1. src/backend/storage/smgr/md.c:1385
--
Maksim Milyutin
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
diff --git a/src/backend/catalog/heap.c b/src/backend/catalog/he
iqueness is guaranteed through global index on partitioned table apart
from the case when the index key are the same as partitioning key (or
index comprises partitioning key in general).
Thanks for your comment. I'll try to propose the first patches as soon
as possible.
--
Maksim M
ulation, though. But IMO it's
not flexible case.
It would be a good thing if a regular table could be partitioned through
separate command. Then your idea would not be restrictive.
--
Maksim Milyutin
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
--
Se
sage-id/CA+TgmoZUwj=qynak+f7xef4w_e2g3xxdmnsnzmzjuinhrco...@mail.gmail.com
2.
https://www.postgresql.org/message-id/2b0d42f2-3a53-763b-c9c2-47139e4b1c2e%40lab.ntt.co.jp
--
Maksim Milyutin
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hacker
n dirty hacks, so the FDW API has to be improved. As for the
extended index support, it doesn't look like a super-hard task.
--
Maksim Milyutin
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresq
01.09.2016 18:58, Tom Lane пишет:
Maksim Milyutin writes:
On Tue, Aug 30, 2016 at 9:34 AM, Maksim Milyutin
mailto:m.milyu...@postgrespro.ru>> wrote:
Yes, but the problem is that nothing gives you the guarantee that at the
moment you decide to handle the interrupt, the QueryDesc stru
On Tue, Aug 30, 2016 at 9:34 AM, Maksim Milyutin
mailto:m.milyu...@postgrespro.ru>> wrote:
On Mon, Aug 29, 2016 at 5:22 PM, maksim
mailto:m.milyu...@postgrespro.ru>
<mailto:m.milyu...@postgrespro.ru
<mailto:m.milyu...@postgrespro.ru>>>
On 2016-08-30 11:22:43 +0300, Maksim Milyutin wrote:
Hi,
On 2016-08-29 18:22:56 +0300, maksim wrote:
Now I complete extension that provides facility to see the current state of
query execution working on external session in form of EXPLAIN ANALYZE
output. This extension works on 9.5 version
nNode() prints only statistics after query execution and
asserts under InstEndLoop(). My patch releases this problem and rewrite
formulas for statistic parameters appropriate to running queries without
affecting regular EXPLAIN outputs.
--
Maksim Milyutin
Postgres Professional: http://www.post
called for running query. Also I complement explain
output, you can see details in README.md in repository.
--
Maksim Milyutin
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
35 matches
Mail list logo
