On Wed, Aug 3, 2022 at 1:43 AM Tom Lane wrote:
> I believe most if not all variants of Unix are
> permissive about the spelling of the encoding part.
I've only seen glibc doing that downcase-and-strip-hyphens thing to
the codeset part of a locale name when looking for locale definition
files.
On 2022-08-02 13:08:41 -0600, Rob Sargent wrote:
> If you can get outside sql, the bulk copy facilities (CopyManager in
> java) is blindingly fast for me.
>
>
> ??
>
>
> I meant using tools other than sql (and psql). I have java code using
> org.postgresql.copy package
I
Logical replication might be another option.
Although I am not sure if that is even possible inside
the samme database.
I know it's tricky inside the same server
(between different databases)
If you can get outside sql, the bulk copy facilities (CopyManager in
java) is blindingly fast for
On 8/2/22 13:59, Rob Sargent wrote:
On 8/2/22 12:51, Thomas Kellerer wrote:
Ron schrieb am 02.08.2022 um 20:37:
AWS RDS Postgresql 12.10
There are no indices or constraints (except for NOT NULL) on table_a.
The two ways that I know are:
INSERT INTO table_a SELECT * FROM table_b;
and
On 8/2/22 13:51, Thomas Kellerer wrote:
Ron schrieb am 02.08.2022 um 20:37:
AWS RDS Postgresql 12.10
There are no indices or constraints (except for NOT NULL) on table_a.
The two ways that I know are:
INSERT INTO table_a SELECT * FROM table_b;
and
\COPY table_a TO '/tmp/table_a.tsv'
On 8/2/22 12:51, Thomas Kellerer wrote:
Ron schrieb am 02.08.2022 um 20:37:
AWS RDS Postgresql 12.10
There are no indices or constraints (except for NOT NULL) on table_a.
The two ways that I know are:
INSERT INTO table_a SELECT * FROM table_b;
and
\COPY table_a TO '/tmp/table_a.tsv'
On 8/2/22 13:41, Adrian Klaver wrote:
On 8/2/22 11:37 AM, Ron wrote:
AWS RDS Postgresql 12.10
There are no indices or constraints (except for NOT NULL) on table_a.
The two ways that I know are:
INSERT INTO table_a SELECT * FROM table_b;
Argh, I got the tables backwards. Should be:
Ron schrieb am 02.08.2022 um 20:37:
AWS RDS Postgresql 12.10
There are no indices or constraints (except for NOT NULL) on table_a.
The two ways that I know are:
INSERT INTO table_a SELECT * FROM table_b;
and
\COPY table_a TO '/tmp/table_a.tsv' WITH (FORMAT BINARY);
\COPY table_b
On 8/2/22 13:41, Rob Sargent wrote:
On 8/2/22 12:37, Ron wrote:
AWS RDS Postgresql 12.10
There are no indices or constraints (except for NOT NULL) on table_a.
The two ways that I know are:
INSERT INTO table_a SELECT * FROM table_b;
and
\COPY table_a TO '/tmp/table_a.tsv' WITH (FORMAT
On 8/2/22 11:37 AM, Ron wrote:
AWS RDS Postgresql 12.10
There are no indices or constraints (except for NOT NULL) on table_a.
The two ways that I know are:
INSERT INTO table_a SELECT * FROM table_b;
and
\COPY table_a TO '/tmp/table_a.tsv' WITH (FORMAT BINARY);
\COPY table_b FROM
On 8/2/22 12:37, Ron wrote:
AWS RDS Postgresql 12.10
There are no indices or constraints (except for NOT NULL) on table_a.
The two ways that I know are:
INSERT INTO table_a SELECT * FROM table_b;
and
\COPY table_a TO '/tmp/table_a.tsv' WITH (FORMAT BINARY);
\COPY table_b FROM
AWS RDS Postgresql 12.10
There are no indices or constraints (except for NOT NULL) on table_a.
The two ways that I know are:
INSERT INTO table_a SELECT * FROM table_b;
and
\COPY table_a TO '/tmp/table_a.tsv' WITH (FORMAT BINARY);
\COPY table_b FROM '/tmp/table_a.tsv' WITH (FORMAT
Install from source code(follow the manual)
system version: Ubuntu 22.04 LTS
pg version: PostgreSQL 15beta2 on x86_64-pc-linux-gnu, compiled by gcc
(Ubuntu 11.2.0-19ubuntu1) 11.2.0, 64-bit
install step:
> ./configure --with-perl --with-python --with-icu
> ICU_CFLAGS='-I/usr/include/unicode'
Durumdara writes:
> Today we found strange database collation names in a server (V11).
> "hu_HU.UTF-8"
> "hu_HU.UTF8"
> "hu_HU.utf8"
Yeah, these are all the same so far as the operating system is
concerned. I believe most if not all variants of Unix are
permissive about the spelling of the
On 7/29/22 04:05, Gianni Ceccarelli wrote:
If you can use bash, or set up some redirections from whatever you're
using to execute ``psql``, you can do::
$ psql somedb --set num=42 <<<'select :num'
Timing is on.
Expanded display is used automatically.
Line style is unicode.
Border
If you can use bash, or set up some redirections from whatever you're
using to execute ``psql``, you can do::
$ psql somedb --set num=42 <<<'select :num'
Timing is on.
Expanded display is used automatically.
Line style is unicode.
Border style is 2.
┌──┐
│ ?column? │
Dear Members!
Today we found strange database collation names in a server (V11).
select -- datname,
distinct datcollate
from pg_database
order by datcollate --, datname;
"hu_HU.UTF-8"
"hu_HU.UTF8"
"hu_HU.utf8"
The PGAdmin also gives us these possible collations in the dialog.
Some of
On 2 Aug 2022, at 17:14, sivapostg...@yahoo.com wrote:
Hello,
I need to create a Foreign Key for a table without enforcing the
constraint for existing data. Few orphan exists in existing data,
which we plan to resolve it later.
We use the following query to create the FK [ Which of course
Hello,
I need to create a Foreign Key for a table without enforcing the constraint for
existing data. Few orphan exists in existing data, which we plan to resolve
it later.
We use the following query to create the FK [ Which of course checks for the
presence of record in referencing table]
19 matches
Mail list logo
