Srinivasa T N writes:
> Hi,
>Partitioning of a table with sequence id as one of its fields is
> supported in postgresql12?
>
> Regards,
> Seenu.
A sequence is really just an 'atomic' number generator, you get the next
value, which is guaranteed to be larger than the last 'nextval' (up
unti
Hi,
I have a parent table with one of the field as ""gid" int4 DEFAULT
nextval('"ami_smart_new".aoi_boundary_gid_seq'::regclass)".
I create child tables which inherit parent and use hash partition. When
I directly insert into child tables, will there be any race condition
causing two child
On Thu, Jun 18, 2020 at 12:00 PM Srinivasa T N wrote:
>
> Hi,
>Partitioning of a table with sequence id as one of its fields is supported
> in postgresql12?
>
Could you please elaborate on your case a bit more?
Regards,
Amul
Hi,
Partitioning of a table with sequence id as one of its fields is
supported in postgresql12?
Regards,
Seenu.
On 6/17/20 7:14 PM, prachi surangalikar wrote:
hello team,
i have tried every thing but still i could not find the solution to
this problem.
i made changes in the pg_hba.conf file also , please help me to solve
this problem.
Should have added to previous post:
Are you sure that you are u
On 6/17/20 7:14 PM, prachi surangalikar wrote:
hello team,
i have tried every thing but still i could not find the solution to
this problem.
i made changes in the pg_hba.conf file also , please help me to solve
this problem.
What is the connection string you are using when you get the err
hello team,
i have tried every thing but still i could not find the solution to
this problem.
i made changes in the pg_hba.conf file also , please help me to solve this
problem.
Michel Pelletier writes:
> In my extension pgsodium I'm defining a custom variable at startup to store
> a key:
> https://github.com/michelp/pgsodium/blob/master/src/pgsodium.c#L1107
> I'm using the flags GUC_NO_SHOW_ALL | GUC_NO_RESET_ALL | GUC_NOT_IN_SAMPLE
> | GUC_DISALLOW_IN_FILE, and a cust
In my extension pgsodium I'm defining a custom variable at startup to store
a key:
https://github.com/michelp/pgsodium/blob/master/src/pgsodium.c#L1107
I'm using the flags GUC_NO_SHOW_ALL | GUC_NO_RESET_ALL | GUC_NOT_IN_SAMPLE
| GUC_DISALLOW_IN_FILE, and a custom "no show" show hook that obscures
"Jim Hurne" writes:
> On one of the instances that is exhibiting the "disk leak" behavior, the
> VACUUM ANALYZE VERBOSE command doesn't generate any output or complete
> before I loose the connection to the database (presumably because I hit a
> connection read timeout). Is it possible to confi
Michael Lewis wrote on 06/16/2020 04:41:16 PM:
> Still, if you run a manual vacuum analyze verbose, what sort of output
do you get?
On one of the instances that is exhibiting the "disk leak" behavior, the
VACUUM ANALYZE VERBOSE command doesn't generate any output or complete
before I loose the
Matthias Apitz writes:
> We encountered that if our ESQL/C written servers see on SELECT or FETCH
> in a row a NULL value, it will raise correctly the error -213 as written
> and explained in
> https://www.postgresql.org/docs/11/ecpg-variables.html#ECPG-INDICATORS
> We catch this error -213 and d
Hello,
We encountered that if our ESQL/C written servers see on SELECT or FETCH
in a row a NULL value, it will raise correctly the error -213 as written
and explained in
https://www.postgresql.org/docs/11/ecpg-variables.html#ECPG-INDICATORS
We catch this error -213 and deal with in.
What we di
Many thanks for your reply.
The last line of the subscriber says:
```
2020-06-17 12:48:02.955 UTC [124] LOG: logical replication apply worker
for subscription "my_subscription" has started
```
Let's keep this on hold for a while, since I guess that it's taking longer
than expected, since it's a
Javi,
What does your PostgreSQL log say about replication?
JD
On Wed, Jun 17, 2020 at 2:07 AM Javi Legido wrote:
> Good morning.
>
> I'm testing logical replication, but after creating subscription nothing
> happens, and I expected replication start.
>
> Details here: https://paste.debian.net/
Susan
You can use -Uvh to upgrade the rpms on the existing machine. You can then
use symlinks to link the expected pgsql data directories. Make sure you
take a backup, and stop the service before you proceed.
JD
On Tue, Jun 16, 2020 at 7:12 AM Susan Joseph
wrote:
> So when I first started wor
Sankar P writes:
> I have a .ndjson file. It is a new-line-delimited JSON file. It is
> about 10GB and has about 100,000 records.
> Some sample records:
> { "key11": "value11", "key12": [ "value12.1", "value12.2"], "key13": {
> "k111": "v111" } } \n\r
> { "key21": "value21", "key22": [ "value22.1"
> In my experience vacuumlo,
https://www.postgresql.org/docs/12/vacuumlo.html, is needed to remove
large objects, before vacuum can remove them from pg_largeobject.
Thanks for the suggestion! vacuumlo deletes any orphaned large objects,
presumably by using lo_unlink. While we don't use vacuuml
Hi Laurenz,
Thank you!
What are reasons for conflicts? Based on documentation seems that the only
reason can be that vacuum removed unused tuples that are in use at standby host
and due to that standby host cannot apply modifications while blocking query
either finishes or will be terminated.
Hi
I have a .ndjson file. It is a new-line-delimited JSON file. It is
about 10GB and has about 100,000 records.
Some sample records:
```
{ "key11": "value11", "key12": [ "value12.1", "value12.2"], "key13": {
"k111": "v111" } } \n\r
{ "key21": "value21", "key22": [ "value22.1", "value22.2"] }
```
On Wed, 2020-06-17 at 08:42 +0300, Toomas Kristin wrote:
> Basically after upgrade to version 11.5 from 10.6 I experience error messages
> on streaming
> replica host “FATAL: terminating connection due to conflict with recovery”
> and
> “ERROR: canceling statement due to conflict with recovery”.
Good morning.
I'm testing logical replication, but after creating subscription nothing
happens, and I expected replication start.
Details here: https://paste.debian.net/1152451/
Any help will be appreciated.
Thanks.
Javier
22 matches
Mail list logo
