Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oIzDU-0003rc-Ef for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Aug 2022 21:14:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oIzDS-0001TE-UU for pgsql-hackers@arkaria.postgresql.org; Tue, 02 Aug 2022 21:14:14 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oIzDS-0001LS-B1 for pgsql-hackers@lists.postgresql.org; Tue, 02 Aug 2022 21:14:14 +0000 Received: from mail-pl1-x634.google.com ([2607:f8b0:4864:20::634]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oIzDO-0001Ms-Tx for pgsql-hackers@postgresql.org; Tue, 02 Aug 2022 21:14:13 +0000 Received: by mail-pl1-x634.google.com with SMTP id v18so14558263plo.8 for ; Tue, 02 Aug 2022 14:14:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=timescale.com; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc; bh=P9nbKuvwqEReGBHgPfn2Kufa8Fet4AEtCgXwow3Ruvk=; b=may2GxC+H5o3ITXZmGXOESco+gWOVx0oT08QLyc7shCgk1fS/a/YxiAU3VnlmQJBVQ MWHQ4C3/S6DiMgTqsV4NvOFFbpLkZUgUVuzkg9LG7/89ppngs0srUWzicuk5mfcuiEdV jmdNjb4zrdsqPOr4YKEUNdr01d6Y1v+GIuqy0UYgJaHpGUs/qL9qd0HZjT5QokugJ+Y0 GKGWz9RMbyfEW3+ERdtsUz1I8PH5I8h8l/pgcZg7FjzzYVUD7I035lxGCRhqAlnbFMU5 wWCJfKarfOmGyQ1z2Ec912s0wMt4YIyxTmnnJAf/nDpwlrySue5d8P1E81aKkkkwZ53d WL0g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc; bh=P9nbKuvwqEReGBHgPfn2Kufa8Fet4AEtCgXwow3Ruvk=; b=hM2WhhUh1pJNXJfovkL1DCeuWq5QNAeWWYq5tlAyAj3O2EZ8K87T5TKgtDYL2FizSU rRKfQSqc6phXjJBZKXudsIVqMvIMCagAm3pW9gvyfWee0SijZNbwoy3F/x6i4UA1XmOC B9gfuIsfTgQSdcqKoc4f9JJvkgJt4Y4d2xKjEykX0KfcknJv0CNumdTx3LnoZ1BzcPCU IO/+qogNzn6PSRf29p+m8uQCS//g6ORroZ/A/0YbUQYul38nyVhlLvDxSbc66uSB8M1J IUbMq0FzrWanWaf8qu7uI8VhNU1VrRc4QR9yuwlIYHlOogqXcmIx1QAModEDMYCnYIQW lQkQ== X-Gm-Message-State: ACgBeo3dtMqfBm0I8M+P50FLB2AGxAmWTJU+mWklb9eXmgdbrda+mtvb OoAlkCUAzi9kPx5Kr96VL+OMAg== X-Google-Smtp-Source: AA6agR7GNz2I0mPteatTXkvUZ+YwQEJE90vW7KqMmLlVkxGTwbTLNiHpHPhRllk7tNUHVwZD72qFuA== X-Received: by 2002:a17:90b:1bc6:b0:1f5:313a:de4b with SMTP id oa6-20020a17090b1bc600b001f5313ade4bmr1465126pjb.4.1659474849864; Tue, 02 Aug 2022 14:14:09 -0700 (PDT) Received: from [192.168.1.21] ([50.39.205.221]) by smtp.gmail.com with ESMTPSA id y129-20020a633287000000b0040c52ff0ba9sm9750665pgy.37.2022.08.02.14.14.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 Aug 2022 14:14:09 -0700 (PDT) Message-ID: <5994dfa9-d2d6-ce0d-0286-174cfe7a5abc@timescale.com> Date: Tue, 2 Aug 2022 14:14:08 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: jsonpath syntax extensions Content-Language: en-US To: Nikita Malakhov , Greg Stark Cc: Nikita Glukhov , PostgreSQL Hackers References: From: Jacob Champion In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk As discussed in [1], we're taking this opportunity to return some patchsets that don't appear to be getting enough reviewer interest. This is not a rejection, since we don't necessarily think there's anything unacceptable about the entry, but it differs from a standard "Returned with Feedback" in that there's probably not much actionable feedback at all. Rather than code changes, what this patch needs is more community interest. You might - ask people for help with your approach, - see if there are similar patches that your code could supplement, - get interested parties to agree to review your patch in a CF, or - possibly present the functionality in a way that's easier to review overall. [For this patchset in particular, it's been suggested to split the extensions up into smaller independent pieces.] (Doing these things is no guarantee that there will be interest, but it's hopefully better than endlessly rebasing a patchset that is not receiving any feedback from the community.) Once you think you've built up some community support and the patchset is ready for review, you (or any interested party) can resurrect the patch entry by visiting https://commitfest.postgresql.org/38/2482/ and changing the status to "Needs Review", and then changing the status again to "Move to next CF". (Don't forget the second step; hopefully we will have streamlined this in the near future!) Thanks, --Jacob [1] https://postgr.es/m/f6344bbb-9141-e8c8-e655-d9baf40c4478%40timescale.com