Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rL3Vp-005s2b-7b for pgsql-committers@arkaria.postgresql.org; Wed, 03 Jan 2024 15:50:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rL3Vn-006Amp-H1 for pgsql-committers@arkaria.postgresql.org; Wed, 03 Jan 2024 15:50:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rL3Vn-006Am8-9R for pgsql-committers@lists.postgresql.org; Wed, 03 Jan 2024 15:50:31 +0000 Received: from mail-qk1-x732.google.com ([2607:f8b0:4864:20::732]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rL3Vk-00FMHv-1h for pgsql-committers@lists.postgresql.org; Wed, 03 Jan 2024 15:50:30 +0000 Received: by mail-qk1-x732.google.com with SMTP id af79cd13be357-78101108e3fso829693085a.1 for ; Wed, 03 Jan 2024 07:50:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dunslane-net.20230601.gappssmtp.com; s=20230601; t=1704297026; x=1704901826; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=zRKdBm9enNQz0Gl8WuMKseoKjJYUyCxxq4wXf80q7k4=; b=UohFDmBWCdzOskriXmZgTHpFw/c94ru4bRbz6Z+o9Tg0WZmpeiqapC5SMv6PJyiYYu ORY1dQRaAmSTnfmLCU6lRk7nLfvQwwRstoEqPwqyclwDXkuICjMEIEDqq2YBeVoND+vL Z3I6g/5WyE47Q9fL0igBrZIPLuScU2ySmD3xQvXus2W5ktiIEGsERPTdJ2vV3snJA5e4 PKKrzzpZqMJ0/A1hJB7+N+5J6xzjs/cg+oTizYvs+ezw2qCGW0dMs318RYYr8T/9n6i2 A367MVu51FCMaQhqFh6zL/WaDtV4E9rGIMPwUYQ8zcFVDFppDS/b0mASLobFJ61JxRh4 bQAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704297026; x=1704901826; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=zRKdBm9enNQz0Gl8WuMKseoKjJYUyCxxq4wXf80q7k4=; b=R6sLALEl1pSQem5cBwepMB1DD+nT3jEPsKyj54eS9Q03kqyFoqHPxJt87yByhkCBkC yd1Oh1Ub/V9oAY1JSkX0Ff6rltfZgqGgS7veNOeYbqELzr8AyL/lGVNPrukc2I9bLHHk to6Ur+vIPToPJyzu8KOYQbWqa5VAvoXd1grNV1ZH2hEB0hKGmBpucstZqXqXAQyZnVVt vn4nXUPpPRiUqYDhQ7It8Wijhc66frIK6imjN/Nu/fHtDscki3GkRc/9NXQbm386oKH/ IAlN7HrrfKrpX76AS5MyI8F66qaPlyHRXCxkPmtkC0TOqw4vwDAsyPsmzlBSCyvGxZix hF4g== X-Gm-Message-State: AOJu0YwU0zJBvE5jazly4Q9Z0BPYngURZ9IbyRZpViRPNSnJHItZyREh hrYTMF3AzvoaH2km28UzKBsCrXsDL/TrxioSzhgRjNKlPfs= X-Google-Smtp-Source: AGHT+IGAZhGLT52gc+mlAnH6Ya/GC73gozumgMidXpNGQuKF79e39f8cv8CKYA1E8LxbgY1V7hPQbg== X-Received: by 2002:a05:620a:124d:b0:77f:289e:79d with SMTP id a13-20020a05620a124d00b0077f289e079dmr18752548qkl.109.1704297025802; Wed, 03 Jan 2024 07:50:25 -0800 (PST) Received: from ?IPV6:2605:a601:91f3:1900::2bb? ([2605:a601:91f3:1900::2bb]) by smtp.googlemail.com with ESMTPSA id m5-20020ae9e005000000b00781df19c062sm1146110qkk.59.2024.01.03.07.50.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 03 Jan 2024 07:50:25 -0800 (PST) Message-ID: Date: Wed, 3 Jan 2024 10:50:24 -0500 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Subject: Re: pgsql: Reorganise jsonpath operators and methods Content-Language: en-US To: Peter Eisentraut , pgsql-committers@lists.postgresql.org References: From: Andrew Dunstan In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2024-01-03 We 05:49, Peter Eisentraut wrote: > Reorganise jsonpath operators and methods > > Various jsonpath operators and methods add various keywords, switch > cases, and documentation entries in some order. However, they are not > consistent; reorder them for better maintainability or readability. > > Author: Jeevan Chalke > Discussion: https://www.postgresql.org/message-id/flat/CAM2+6=XjTyqrrqHAOj80r0wVQxJSxc0iyib9bPC55uFO9VKatg@mail.gmail.com This appears to have broken cross version upgrade. crake is seeing: pg_dump: error: Dumping the contents of table "tab_core_types" failed: PQgetResult() failed. pg_dump: detail: Error message from server: ERROR:  unrecognized jsonpath item type: 126 pg_dump: detail: Command was: COPY public.tab_core_types (point, line, lseg, box, openedpath, closedpath, polygon, circle, date, "time", "timestamp", timetz, timestamptz, "interval", "json", jsonb, jsonpath, inet, cidr, macaddr8, macaddr, int2, int4, int8, float4, float8, pi, "char", bpchar, "varchar", name, text, bool, bytea, "bit", varbit, money, refcursor, int2vector, oidvector, tsvector, tsquery, uuid, regclass, regtype, regrole, oid, tid, xid, cid, txid_snapshot, pg_lsn, cardinal_number, character_data, sql_identifier, time_stamp, yes_or_no, planets, insenum, int4range, int8range, float8range, numrange, textrange, cashrange, daterange, tsrange, tstzrange, arrayrange) TO stdout; pg_dumpall: error: pg_dump failed on database "regression", exiting (I also need to make sure we capture the output of pg_dumpall) cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com