Thanks. Nice one. Would not have thought to try.
On 8/9/24 14:13, yudhi s wrote:
Hello,
It's version 15.4 postgres. Where we have an insert working fine, but
then a similar insert with the same 'timestamp' value, when trying to be
executed through merge , it fails stating "You will need to rewrite or
cast the expression.". Why so?
*Example
On Fri, Aug 9, 2024 at 2:14 PM yudhi s wrote:
>
> Why so?
>
Because you stuck a CTE in between the column list of the insert - where
types are known - and the values command - where types are unknown since
you didn't specify them. As the row comes out of the CTE every column must
have a known t
Hello,
It's version 15.4 postgres. Where we have an insert working fine, but then
a similar insert with the same 'timestamp' value, when trying to be
executed through merge , it fails stating "You will need to rewrite or cast
the expression.". Why so?
*Example:-*
https://dbfiddle.uk/j5S7br-q
CRE
On Fri, Aug 9, 2024 at 9:19 PM Greg Sabino Mullane
wrote:
> On Fri, Aug 9, 2024 at 6:39 AM Lok P wrote:
>
>> Thank you so much. Will definitely try to evaluate this approach. The
>> Only concern I have is , as this data is moving downstream with exactly the
>> same data type and length , so will
If you want to convert your table name into a timestamp, you don't need
substring or similar. This also works:
=# select to_date('table_part_p2024_08_08', '"table_part_p""_"MM"_"DD');
to_date
2024-08-08
(1 row)
But as Greg said, your strings are perfectly sortable.
On Thu, A
On Fri, Aug 9, 2024 at 1:02 AM David Rowley wrote:
> On Fri, 9 Aug 2024 at 02:12, Christophe Pettus wrote:
> > VACUUM FULL takes an exclusive lock on the table that it is operating
> on. It's possible that a connection becomes blocked on that exclusive lock
> waiting for the VACUUM FULL to fini
On Fri, Aug 9, 2024 at 6:39 AM Lok P wrote:
> Thank you so much. Will definitely try to evaluate this approach. The Only
> concern I have is , as this data is moving downstream with exactly the same
> data type and length , so will it cause the downstream code to break while
> using this column i
On 8/9/24 03:26, Jim Vanns wrote:
Hi pggen community!
I am struggling with this error almost daily now and despite various
efforts, not succeeding in avoiding or dealing with it;
My questions are;
1) How should I be managing this? Although not new to PG, I am new to
this particular problem
On Fri, 9 Aug 2024 at 06:20, Ron Johnson wrote:
>
> What if the partitions aren't all rationally named? There *must* be a
> pg_* table out there which contains the partition boundaries...
>
>
The pg_class column relpartbound contains an internal representation of the
partition boundary, when app
To clear up any confusion, I tried the reductions as hinted in the
error message and after a few iterations still faced the same error.
Also, re. the sample configuration I provided - this is the result of
said iterations after initially using the stock values from the PGDG
RPM.
Jim
On Fri, 9 Aug
On Tue, Aug 6, 2024 at 4:48 PM Dominique Devienne wrote:
> On Tue, Aug 6, 2024 at 4:31 PM Tom Lane wrote:
> > Dominique Devienne writes:
> > Indeed, that's an oversight, and there's a number of other things
> > we added to libpq-fe.h between 16 and 17 that probably deserve
> > their own LIBPQ_HA
On Fri, 2024-08-09 at 17:18 +0800, 王瞿 wrote:
> Searching for the above.
> The
> Does anyone kown where I can find it？
> Needed for a project to work with Postgresql 14.
The client libraries for this version are in
https://download.postgresql.org/pub/repos/yum/14/redhat/rhel-8-x86_64/postgresql14-
On Tue, Aug 6, 2024 at 10:53 AM Dominique Devienne wrote:
> On Mon, Aug 5, 2024 at 2:26 PM David Rowley wrote:
> > Meson is now the only available method for Visual Studio builds."
>
> Thanks David. My colleague figured it out, thanks to your pointers. Cheers,
> --DD
FYI, we ran into a surprisi
This helps. Thank you very much.
On Fri, 9 Aug 2024 at 02:15, Greg Sabino Mullane wrote:
> _MM_DD is already setup for sorting, so just do:
>
> SELECT table_name FROM information_schema.tables WHERE table_name ~
> 'table_part_p' ORDER BY 1 DESC;
>
> If you need to grab the numbers:
>
> SELEC
On Fri, Aug 9, 2024 at 2:06 AM Greg Sabino Mullane
wrote:
> On Thu, Aug 8, 2024 at 2:39 PM Lok P wrote:
>
>> Can anybody suggest any other possible way here.
>>
>
> Sure - how about not changing the column type at all?
>
> > one of the columns from varchar(20) to varchar(2)
>
> ALTER TABLE fooba
Hi pggen community!
I am struggling with this error almost daily now and despite various
efforts, not succeeding in avoiding or dealing with it;
ERROR: multixact "members" limit exceeded
DETAIL: This command would create a multixact with 2 members, but the
remaining space is only enough for 0 m
Searching for the above.
The
Does anyone kown where I can find it？
Needed for a project to work with Postgresql 14.
Thanks.
| |
wangq...@126.com
|
|
邮箱：wangq...@126.com
|
18 matches
Mail list logo
