On Mon, May 23, 2022, 11:33 AM Rama Krishnan wrote:
> Hi,
>
> After pg_repack do we face any perfomancr issue or any other issues in
> production DB
>
Using pg 14, is it easy (possible) to list the tablespaces used in a
custom format dump. Are the definitions included?
Thanks,
On 5/23/22 9:45 AM, Rob Sargent wrote:
Using pg 14, is it easy (possible) to list the tablespaces used in a
custom format dump. Are the definitions included?
https://www.postgresql.org/docs/14/app-pgdump.html
"pg_dump only dumps a single database. To back up an entire cluster, or
to back up
On 5/23/22 10:50, Adrian Klaver wrote:
On 5/23/22 9:45 AM, Rob Sargent wrote:
Using pg 14, is it easy (possible) to list the tablespaces used in a
custom format dump. Are the definitions included?
https://www.postgresql.org/docs/14/app-pgdump.html
"pg_dump only dumps a single database. To b
On 5/23/22 9:54 AM, Rob Sargent wrote:
On 5/23/22 10:50, Adrian Klaver wrote:
Roger that, but does the dump of a database name the tablespaces from
which the objects were retrieved? And if so, is that accessible?
https://www.postgresql.org/docs/14/app-pgrestore.html
"--no-tablespaces
On 5/23/22 11:00, Adrian Klaver wrote:
On 5/23/22 9:54 AM, Rob Sargent wrote:
On 5/23/22 10:50, Adrian Klaver wrote:
Roger that, but does the dump of a database name the tablespaces from
which the objects were retrieved? And if so, is that accessible?
https://www.postgresql.org/docs/14/a
On 5/23/22 10:01 AM, Rob Sargent wrote:
On 5/23/22 11:00, Adrian Klaver wrote:
On 5/23/22 9:54 AM, Rob Sargent wrote:
On 5/23/22 10:50, Adrian Klaver wrote:
Roger that, but does the dump of a database name the tablespaces from
which the objects were retrieved? And if so, is that accessible?
Hello!
Peter J. Holzer ezt írta (időpont: 2022. máj. 11., Sze,
0:44):
> On 2022-05-07 15:02:09 +0200, Durumdara wrote:
>
> > So in the new trigger we can't load them all with:
>
> How do you get a new trigger on one table but not the new columns on the
> other table? Wouldn't you update both at
On 5/23/22 11:07, Adrian Klaver wrote:
On 5/23/22 10:01 AM, Rob Sargent wrote:
On 5/23/22 11:00, Adrian Klaver wrote:
On 5/23/22 9:54 AM, Rob Sargent wrote:
On 5/23/22 10:50, Adrian Klaver wrote:
Roger that, but does the dump of a database name the tablespaces
from which the objects were re
Hi.
I want to secure connections to postgress server usings SSL.
My server is deployed on google cloud behind SSL load balancer, which
terminates SSL connections (using SSL certificates, issued by google)
and forwards decrypted traffic to the posgres server.
I can connect without problems fro
Adrian Klaver writes:
> On 5/23/22 9:54 AM, Rob Sargent wrote:
>> Roger that, but does the dump of a database name the tablespaces from
>> which the objects were retrieved? And if so, is that accessible?
> Would indicate it does. I don't have cluster set up with tablespaces to
> test, but I wou
"dzagas...@gmail.com" writes:
> I want to secure connections to postgress server usings SSL.
> My server is deployed on google cloud behind SSL load balancer, which
> terminates SSL connections (using SSL certificates, issued by google)
> and forwards decrypted traffic to the posgres server.
> B
Hello!
I need to log some row changes in a table with JSON format (row_to_json).
In the Before Update I can select the row into a column with JSON format.
And in After Update I can log this column into an archive table.
Plus I have the prior data in the JSON_TEXT field.
It's ok.
FUNCTION Before
Ah, thanks.
This will make thing more complex.
On 23.05.2022 20:32, Tom Lane wrote:
"dzagas...@gmail.com" writes:
I want to secure connections to postgress server usings SSL.
My server is deployed on google cloud behind SSL load balancer, which
terminates SSL connections (using SSL certificate
On 5/23/22 10:35 AM, Durumdara wrote:
Hello!
I need to log some row changes in a table with JSON format (row_to_json).
In the Before Update I can select the row into a column with JSON format.
And in After Update I can log this column into an archive table.
Plus I have the prior data in the JSO
On 5/23/22 11:29, Tom Lane wrote:
AFAICS, the output produced by -l doesn't mention objects' tablespaces.
You could see them by extracting the plain text archive and grepping
for object comments that include a tablespace name:
pg_restore -s -f - archive_file | grep Tablespace:
It looks to me l
On 5/23/22 10:19 AM, Rob Sargent wrote:
On 5/23/22 11:07, Adrian Klaver wrote:
On 5/23/22 10:01 AM, Rob Sargent wrote:
On 5/23/22 11:00, Adrian Klaver wrote:
On 5/23/22 9:54 AM, Rob Sargent wrote:
On 5/23/22 10:50, Adrian Klaver wrote:
This is great news. I do have pg14. I thought you
On 5/23/22 11:51, Adrian Klaver wrote:
On 5/23/22 10:19 AM, Rob Sargent wrote:
On 5/23/22 11:07, Adrian Klaver wrote:
On 5/23/22 10:01 AM, Rob Sargent wrote:
On 5/23/22 11:00, Adrian Klaver wrote:
On 5/23/22 9:54 AM, Rob Sargent wrote:
On 5/23/22 10:50, Adrian Klaver wrote:
This is gre
On 5/23/22 11:04 AM, Rob Sargent wrote:
Thanks Adrian. There's enough wiggle room in there for me to at least
try the restore. Linus file command tells me
db.dump: PostgreSQL custom database dump - v1.13-0
The
pg_restore -l
command will show the relevant information at top of file so
Rob Sargent writes:
> Thanks Adrian. There's enough wiggle room in there for me to at least
> try the restore. Linus file command tells me
> db.dump: PostgreSQL custom database dump - v1.13-0
> That dump was from a version 10 server. Any guess at how that "v1.13-0"
> relates to the serve
On 5/23/22 12:15, Tom Lane wrote:
Rob Sargent writes:
Thanks Adrian. There's enough wiggle room in there for me to at least
try the restore. Linus file command tells me
db.dump: PostgreSQL custom database dump - v1.13-0
That dump was from a version 10 server. Any guess at how that "v1.13
On 5/23/22 11:31, Rob Sargent wrote:
On 5/23/22 12:15, Tom Lane wrote:
pg_restore -f - db.dump | head
which should provide some comments telling you the originating
server version and pg_dump version.
regards, tom lane
OK, back to reality: version 10 dump.
The out
> On May 23, 2022, at 12:59 PM, Adrian Klaver wrote:
>
> On 5/23/22 11:31, Rob Sargent wrote:
>> On 5/23/22 12:15, Tom Lane wrote:
>
>>>
>>> pg_restore -f - db.dump | head
>>>
>>> which should provide some comments telling you the originating
>>> server version and pg_dump version.
>>>
>>>
On 5/23/22 12:26, Rob Sargent wrote:
As to older version, how are you installing Postgres?
Much appreciated,
rjs
Yeah, that’s part of the problem. /I’m/ not installing postgres, another
group has that control. I can get the answer for version 14 but maybe
not for version 10. Curren
On 5/23/22 13:47, Adrian Klaver wrote:
On 5/23/22 12:26, Rob Sargent wrote:
As to older version, how are you installing Postgres?
Much appreciated,
rjs
Yeah, that’s part of the problem. /I’m/ not installing postgres,
another group has that control. I can get the answer for version 1
CREATE DOMAIN testdomain AS text;
--asume the default collation is as per show LC_COLLATE;
– on my pc, it is C.UTF-8.
--So the testdomain will be collation "C.UTF-8"
=> \d collate_test1
Table "test.collate_test1"
Column | Type | Collation | Nullable | Default
--
On Monday, May 23, 2022, jian he wrote:
> CREATE DOMAIN testdomain AS text;
>
> --asume the default collation is as per show LC_COLLATE;
>
> – on my pc, it is C.UTF-8.
>
> --So the testdomain will be collation "C.UTF-8"
>
>
> => \d collate_test1
>
> Table "test.collate_t
"David G. Johnston" writes:
> On Monday, May 23, 2022, jian he wrote:
>> CREATE DOMAIN testdomain AS text;
>> --asume the default collation is as per show LC_COLLATE;
>> – on my pc, it is C.UTF-8.
>> --So the testdomain will be collation "C.UTF-8"
> My reading of the docs say this is consistent
Dear Adrian!
Thank you for the information. For me the main question is that:
Can I execute an UPDATE in the AFTER INSERT trigger procedure?
Or is this confuses PGSQL, because prior operation (INSERT) isn't fully
finished?
Thank you!
BR,
dd
Adrian Klaver ezt írta (időpont: 2022. máj.
23., H,
29 matches
Mail list logo
