On 5/5/23 18:14, Marc Millas wrote:
Hi,
postgres 14.2 on Linux redhat
temp_file_limit set around 210 GB.
a select request with 2 left join have crashed the server (oom killer)
after the postgres disk occupation did grow from 15TB to 16 TB.
The result of EXPLAIN would be helpful.
What ar
Hi,
postgres 14.2 on Linux redhat
temp_file_limit set around 210 GB.
a select request with 2 left join have crashed the server (oom killer)
after the postgres disk occupation did grow from 15TB to 16 TB.
What are the cases where postgres may grow without caring about
temp_file_limit ?
thanks,
On Fri, May 5, 2023 at 7:50 PM Evgeny Morozov
wrote:
> The OID of the bad DB ('test_behavior_638186279733138190') is 1414389 and
> I've uploaded base/1414389/pg_filenode.map and also base/5/2662 (in case
> that's helpful) as https://objective.realityexists.net/temp/pgstuff1.zip
Thanks. That pg
On 5/5/23 10:55 AM, Rajmohan Masa wrote:
Hi Adrian,
Are both the above the same for the original and restored database?
We are using a Windows server so By Using the PgAdmin4 tool, I'm taking
Backup and restore.
From here
https://www.pgadmin.org/docs/pgadmin4/7.1/restore_dialog.html
you
On 5/5/23 10:55 AM, Rajmohan Masa wrote:
Please reply to list also.
Ccing list.
Hi Adrian,
Are both the above the same for the original and restored database?
No,
*
*
*Backup Server Details:*
Postgres version : *PostgreSQL 14.5*
OS and version : *Windows server 2019 Datacenter*
*Restore Server
On 5/5/23 08:35, Rajmohan Masa wrote:
Hi Team,
I took Postgres database Backup through Directory format with
compression.These are the details
Postgres version?
OS and version?
Are both the above the same for the original and restored database?
Provide the commands you used to arrive at siz
Hi Team,
I took Postgres database Backup through Directory format with
compression.These are the details
Database Size: *3985 GB*
Backup file Size will be* 212 GB.*
After that I Restored this backup file (212GB), but I'm getting Database
size will be 456 GB.
So immediately I checked with *Table B
On 5/5/23 06:49, sujay kadam wrote:
Hi Team.
I have enabled SSL in postgres on a different port using pgbouncer.
I have changed the default port to 6432 and made it SSL enabled and
configured pgbouncer to listen port 5432 which is non-ssl.
But we are connecting directly using port, not by up
"David G. Johnston" writes:
> On Fri, May 5, 2023 at 6:55 AM Sky Lendar wrote:
>> Notice that 12 is missing in the list.
> Since your DISTINCT ON *subquery* doesn't specify an ordering which of
> those two are chosen as the representative record for M31 is
> non-determinstic.
> If you want to e
Thank you for the clarification.
Le ven. 5 mai 2023 à 16:16, David G. Johnston
a écrit :
> On Fri, May 5, 2023 at 6:55 AM Sky Lendar wrote:
>
>> Hi there ans thx for reading and answering this post if you can:
>>
>> Let's regard an example of a table (stars) containing a code for a star
>> (sym
On Fri, May 5, 2023 at 6:55 AM Sky Lendar wrote:
> Hi there ans thx for reading and answering this post if you can:
>
> Let's regard an example of a table (stars) containing a code for a star
> (symb)
> and its index (nb) in a file.
>
>
> nb |symb
> +
> 0 | alTau
> 1 | al
On Fri, May 5, 2023 at 9:50 AM sujay kadam wrote:
>
> I have enabled SSL in postgres on a different port using pgbouncer.
>
> I have changed the default port to 6432 and made it SSL enabled and
> configured pgbouncer to listen port 5432 which is non-ssl.
>
> But we are connecting directly using p
Hi there ans thx for reading and answering this post if you can:
Let's regard an example of a table (stars) containing a code for a star
(symb)
and its index (nb) in a file.
nb |symb
+
0 | alTau
1 | alTau
2 | bePer
3 | alSco
4 | alLeo
5 | alCMa
6 | alVir
7 |
Hi Team.
I would like to inform you that I have successfully enabled SSL on a
different port in Postgres using pgbouncer. Specifically, I have modified
the default port to 6432 and configured it for SSL while setting up
pgbouncer to listen to a non-SSL port at 5432.
However, I have noticed that s
Hi Team.
I have enabled SSL in postgres on a different port using pgbouncer.
I have changed the default port to 6432 and made it SSL enabled and
configured pgbouncer to listen port 5432 which is non-ssl.
But we are connecting directly using port, not by uploading a certificate
or setting up SSL
Hi,
similar to pg_get_functiondef ( *func* oid ) → text
is there any function to get the role definition?
On 5/05/2023 10:38 am, Andrew Gierth wrote:
> sudo -u postgres psql -w -p 5434 -d "options='-P'"
> (make that -d "dbname=whatever options='-P'" if you need to specify
> some database name; or use PGOPTIONS="-P" in the environment.)
Thanks, good to know! Unfortunately that also fails:
# sudo -u p
On Fri, May 5, 2023 at 9:23 AM Luca Ferrari wrote:
>
> Hi all,
> this may be tribial, but I'm seeing connections from ::1 in
> pg_stat_activity, and I've never realiuzed that psql converts
> "localhost" in IPv6.
> Is there a way to "force" the hostname localhost to appear as IPv4 or
> am I missing
> "Evgeny" == Evgeny Morozov writes:
Evgeny> Indeed, I cannot get that far due to the same error. I read
Evgeny> about ignore_system_indexes, but...
Evgeny> # sudo -u postgres psql -w -p 5434 -c "set ignore_system_indexes=on";
Evgeny> ERROR: parameter "ignore_system_indexes" cannot be s
On 5/05/2023 2:02 am, Thomas Munro wrote:
> On Fri, May 5, 2023 at 11:15 AM Thomas Munro wrote:
>> What does select
>> pg_relation_filepath('pg_class_oid_index') show in the corrupted
>> database, base/5/2662 or something else?
> Oh, you can't get that far, but perhaps you could share the
> pg_fil
Hi all,
this may be tribial, but I'm seeing connections from ::1 in
pg_stat_activity, and I've never realiuzed that psql converts
"localhost" in IPv6.
Is there a way to "force" the hostname localhost to appear as IPv4 or
am I missing something?
I've tested it also with a Perl program, and specifyin
21 matches
Mail list logo
