On 7/8/20 12:27 PM, Luiz Hugo Ronqui wrote:
Hello all!
I’m experimenting with options to upgrade databases from older (v9.x) to
more recent (probably v11) versions of PostgreSql and, partitioning some
large tables during the process.
The idea was:
1)To make a dump of the old database, wich
Hello all!
I'm experimenting with options to upgrade databases from older (v9.x) to
more recent (probably v11) versions of PostgreSql and, partitioning some
large tables during the process.
The idea was:
1) To make a dump of the old database, wich I've done with the custom
format
2
Tom Lane schrieb am 08.07.2020 um 18:41:
Somehow, the reading file is being left in binary mode and thus it's
failing to convert \r\n back to plain \n.
Now the weird thing about that is I'd have expected "r" and "w" modes
to imply Windows text mode already, so that I'd have figured that
_setmode
=?UTF-8?Q?FOUTE_K=2E_Jaur=C3=A8s?= writes:
> After many tests of proposal solutions, I am not able to solve the issue.
> Seems that It is a bug ?
I agree. But it's not *our* bug: Postgres is merely reporting what the
OS told it. File a kernel bug with your OS vendor.
re
Thomas Kellerer writes:
> I noticed the following strage output when running Postgres 12.3 (not psql)
> on Windows
> postgres=# select pg_current_logfile();
> pg_current_logfile
>
> pg_log/postgresql-2020-07-08.log\r
> (1 row)
>
On 7/8/20 7:09 AM, Yorwerth, Adam wrote:
Hi Everyone,
We’re trying to solve a problem that relies on BigSerial and txid (as
returned by txid_current() ) values being issued consistently.
Is it possible for two transactions to interleave their issuance of
these two variables?
For example:
On Wed, Jul 8, 2020 at 8:18 AM Yorwerth, Adam
wrote:
> Is it possible for two transactions to interleave their issuance of these
> two variables?
>
>
>
> Is it possible for transaction 1 to be issued txid 1001 and offset 12 and
> transaction 2 to be issued txid 1002 and offset 11?
>
Given all of
Hi Everyone,
We’re trying to solve a problem that relies on BigSerial and txid (as returned
by txid_current() ) values being issued consistently.
Is it possible for two transactions to interleave their issuance of these two
variables?
For example:
Schema:
CREATE TABLE EXAMPLE(
offset bigin
Hello Raf, Tom,
After many tests of proposal solutions, I am not able to solve the issue.
Seems that It is a bug ?
Le jeu. 2 juil. 2020 à 01:59, Tom Lane a écrit :
> raf writes:
> > FOUTE K. Jaurès wrote:
> >> The result of df -i
> >>
> >> Sys. de fichiers Inœuds IUtil. ILibre IUti% Monté
On 7/8/20 6:45 AM, Adrian Klaver wrote:
On 7/8/20 6:05 AM, Thomas Kellerer wrote:
Hello,
I noticed the following strage output when running Postgres 12.3 (not
psql) on Windows
postgres=# select pg_current_logfile();
pg_current_logfile
-
On 7/8/20 6:05 AM, Thomas Kellerer wrote:
Hello,
I noticed the following strage output when running Postgres 12.3 (not psql) on
Windows
postgres=# select pg_current_logfile();
pg_current_logfile
pg_log/postgresql-2020-07-08.log
Hello,
I noticed the following strage output when running Postgres 12.3 (not psql) on
Windows
postgres=# select pg_current_logfile();
pg_current_logfile
pg_log/postgresql-2020-07-08.log\r
(1 row)
Note the "\r" at the end of the
I am happy to help with testing the bash script and producing a
documentation.
Regards,
Shao
On Sat, 20 Jun 2020 at 02:38, David G. Johnston
wrote:
> On Friday, June 19, 2020, pepevo wrote:
>
>> But everything can run by script on the server, right?
>>
>
> Separation of concerns. The server
13 matches
Mail list logo
