On Mon, Dec 11, 2023 at 10:34 PM Chris Travers
wrote:
> On Tue, Dec 12, 2023 at 2:11 AM Ron Johnson
> wrote:
>
>> On Mon, Dec 11, 2023 at 4:41 AM Dominique Devienne
>> wrote:
>>
>>> On Sun, Dec 10, 2023 at 5:56 PM Ron Johnson
>>> wrote:
>>>
* We departitioned because SELECT statements
On Tue, Dec 12, 2023 at 2:11 AM Ron Johnson wrote:
> On Mon, Dec 11, 2023 at 4:41 AM Dominique Devienne
> wrote:
>
>> On Sun, Dec 10, 2023 at 5:56 PM Ron Johnson
>> wrote:
>>
>>> * We departitioned because SELECT statements were *slow*. All
>>> partitions were scanned, even when the partition
On 12/11/23 10:54 AM, Igniris Valdivia Baez wrote:
hello to all, thanks for your answers i've changed the encoding using this:
ALTER DATABASE testdb
SET client_encoding = WIN1252;
now when we try to select data from a table we get this error:
ERROR: character with byte sequence 0xe2 0x80
hello to all, thanks for your answers i've changed the encoding using this:
ALTER DATABASE testdb
SET client_encoding = WIN1252;
now when we try to select data from a table we get this error:
ERROR: character with byte sequence 0xe2 0x80 0x8b in encoding "UTF8"
has no equivalent in encoding
On Mon, Dec 11, 2023 at 4:41 AM Dominique Devienne
wrote:
> On Sun, Dec 10, 2023 at 5:56 PM Ron Johnson
> wrote:
>
>> * We departitioned because SELECT statements were *slow*. All
>> partitions were scanned, even when the partition key was specified in the
>> WHERE clause.
>>
>
> Surely that's
Ian Lawrence Barwick writes:
> 2023年12月11日(月) 18:09 Ayush Vatsa :
>> ./config.status: line 486: syntax error near unexpected token `)'
>> ./config.status: line 486: ` *\'*) ac_optarg=`$as_echo "$ac_optarg" | sed
>> "s/'/'''/g"` ;;'
> You should provide, at the very least, the following
2023年12月11日(月) 18:09 Ayush Vatsa :
>
> Hello, PostgreSQL community,
> I'm reaching out to you about an issue I've had while trying to configure
> PostgreSQL by cloning its files from the GitHub repository.
> During the configuration process, I encountered an error message that
> appeared to be
\copy in psql just wraps PostgreSQL's COPY FROM STDIN.
if you are trying to do it from your own client program it is trivial to
change to that call instead.
On Mon, Dec 11, 2023 at 4:09 PM Vincent Veyron
wrote:
> On Fri, 8 Dec 2023 10:45:28 -0500
> David Gauthier wrote:
> >
> > I'm trying to
On Sun, Dec 10, 2023 at 5:56 PM Ron Johnson wrote:
> * We departitioned because SELECT statements were *slow*. All partitions
> were scanned, even when the partition key was specified in the WHERE clause.
>
Surely that's no the case on newer PostgreSQL, is it? Otherwise what's the
point of
On Fri, 8 Dec 2023 10:45:28 -0500
David Gauthier wrote:
>
> I'm trying to run a PG client side "\copy" command from a perl script. I
> tried using $dbh->do("\\copy ...") but it barffed when it saw the '\'...
> ERROR: syntax error at or near "\"
>
> I can do this with a command line approach,
Hello, PostgreSQL community,
I'm reaching out to you about an issue I've had while trying to configure
PostgreSQL by cloning its files from the GitHub repository.
During the configuration process, I encountered an error message that
appeared to be related to a syntax issue within the
Thank you for your response.
Apology if it sounds silly, but is it advisable to use just one database in
this flow, say for e.g snowflake for olap usecase and use a cache
layer(like reddish) on top of it to cater our oltp Usecase, rather having a
dedicated oltp database like Aurora postgresql?
12 matches
Mail list logo
