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 1p3Vur-0006Zc-3k for pgsql-general@arkaria.postgresql.org; Fri, 09 Dec 2022 05:27:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1p3Vup-0002JG-V3 for pgsql-general@arkaria.postgresql.org; Fri, 09 Dec 2022 05:27:19 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1p3Vup-0002J6-IB for pgsql-general@lists.postgresql.org; Fri, 09 Dec 2022 05:27:19 +0000 Received: from mail-qt1-x834.google.com ([2607:f8b0:4864:20::834]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1p3Vun-0001R2-H3 for pgsql-general@lists.postgresql.org; Fri, 09 Dec 2022 05:27:19 +0000 Received: by mail-qt1-x834.google.com with SMTP id cg5so2865565qtb.12 for ; Thu, 08 Dec 2022 21:27:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=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=NhLzqDpMxNJ/UJAPkZVY0DUW3j20YoR55UUooK0I/Qs=; b=UaqWY3KtqaUFxbYZMJVjReJx5BnAZ80WwEnTdHlTfQUm6sEcVQWVBX0j35J2H1kdp9 eHPcADux/BbtDZkwSaRAPMJ1ouZ2k9OkCnqdIYYJV9LRfwpguFpheVwVi7rKjlCPzLQ4 UM00bN3LW9Rxq60rl1RW3OCC2YwnyU+0EcToOgvScsvLXwBL5oQpgDBKIoNUuczFccTW S3IJeW8owv+TJVwVfBcS2AKq2myzW2rJmQVVuzIee/D513rUzoYy+wRX530vsVvn/hKG ZurNSKMN5k8xUXd7HjpiWNFa9IPLsHekyUp8gXxFwY2VO1xvrNJ5ETIjxeXOnetjvLdj s8dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=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=NhLzqDpMxNJ/UJAPkZVY0DUW3j20YoR55UUooK0I/Qs=; b=sHqll3/+wTvTDNMP41uqAmRD15E4+Az7Sa1P7Cui+kqavG7HvB7k63p752JsytKJhO IZL6C1WT0/CF8zZ32ipthA83rsQrbNGyoC6akSyhO+hxKsHB3FHEFxEnQ0xPUFxyKEQF 8AhF1e5WjoLPoR9kYck+UvTZmVQt9ycPCtR5t/+ejl+S9hOOaRw1eIf8luCExrE9zxMk gLrFCR+u1uUTokak3KTt82L56KuGzbzeqe48BAsqVWe3O3JD+LtZ2uozsUvwOcpP7SrC 4zahZmhvuI+n9P+nCDsGQv8kapcZR28081B7tDETkZ1nXV1SnNOzZHcisza4WfNwtniO NYOQ== X-Gm-Message-State: ANoB5pkWJhqFI4RbVERMHBCP8of/MWb3ViJKjPmwXtsdrqu3CYe6cGbp +1n+wML0PpKSqRG7eq7kFPNtR5WcUQY= X-Google-Smtp-Source: AA0mqf5MGS1mfhdJVN06zzmengoXk5f2jfoFXADosKdnNFMOwQSHsA9AGyDRjixCyHk+k093U3lGYQ== X-Received: by 2002:ac8:5c83:0:b0:3a6:c4eb:2e52 with SMTP id r3-20020ac85c83000000b003a6c4eb2e52mr9090094qta.43.1670563635189; Thu, 08 Dec 2022 21:27:15 -0800 (PST) Received: from ?IPV6:2600:1700:bd2c:b810::43? ([2600:1700:bd2c:b810::43]) by smtp.googlemail.com with ESMTPSA id de17-20020a05620a371100b006fae7e6204bsm366048qkb.108.2022.12.08.21.27.14 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 08 Dec 2022 21:27:14 -0800 (PST) Content-Type: multipart/alternative; boundary="------------dHmvbf6ts9fLjzafevYWY3o1" Message-ID: Date: Thu, 8 Dec 2022 23:27:14 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: Inheritance pg_largeobject table Content-Language: en-US To: pgsql-general@lists.postgresql.org References: <988914804de248e2af8e2c4d2be915c6@cra-arc.gc.ca> From: Ron In-Reply-To: <988914804de248e2af8e2c4d2be915c6@cra-arc.gc.ca> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------dHmvbf6ts9fLjzafevYWY3o1 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 12/8/22 23:08, Zhao, Bing wrote: > > *Categorization: Unclassified * > > We are running PG11.11, and have more than 50T LO data about load into the > pg_largeobject table. But 32T is the limitation. > > We have created couple child tables that using inheritance to > pg_largeobject, and we have tried use triggers(insert or update) to put > into child tables. It doesn’t work by use LO functions, ex lo_put, > lo_create…seems never got triggered. But works with insert statement into > the pg_largeobject. > > If we move LO data from root table to child, lo_get will break. > > Any ideas? > Out of curiosity, why inheritance instead of declarative partitioning? -- Angular momentum makes the world go 'round. --------------dHmvbf6ts9fLjzafevYWY3o1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 12/8/22 23:08, Zhao, Bing wrote:

Categorization: Unclassified

We are running PG11.11, and have more than 50T LO data about load into the pg_largeobject table. But 32T is the limitation.

We have created couple child tables that using inheritance to pg_largeobject, and we have tried use triggers(insert or update) to put into child tables. It doesn’t work by use LO functions, ex lo_put, lo_create…seems never got triggered. But works with insert statement into the pg_largeobject.

If we move LO data from root table to child, lo_get will break.

 

Any ideas?


Out of curiosity, why inheritance instead of declarative partitioning?

--
Angular momentum makes the world go 'round.
--------------dHmvbf6ts9fLjzafevYWY3o1--