Hi All,
Any one can give me an idea how we can generate the alter sequence and drop
constraints scripts /statements for a schema tables using ora2pg.conf
Regards,
Daulat
On 6/19/19 8:56 PM, William Denton wrote:
When inserting up updating a row with not null constraints that are not
satisfied, postgres reflects the values in the row in the error DETAIL.
postgres=# create database test;
CREATE DATABASE
postgres=# \c test;
psql (11.1 (Debian 11.1-3.pgdg90+1), ser
When inserting up updating a row with not null constraints that are not
satisfied, postgres reflects the values in the row in the error DETAIL.
postgres=# create database test;
CREATE DATABASE
postgres=# \c test;
psql (11.1 (Debian 11.1-3.pgdg90+1), server 11.2)
You are now connected to database "
> "Rob" == Rob Sargent writes:
>>> local all all trust
Rob> That line has four values and the header has 5.
That's standard for "local" lines, which lack an ADDRESS field.
--
Andrew (irc:RhodiumToad)
Hi Adrian, thanks for responding.
How would I restrict access to the SECURITY DEFINER function? If it can be
called by the trigger, it can be called by the user as well I would think.
Same issue as access to the table itself only now with a superuser
intermediary, right?
On Tue, Jun 18, 2019 at
On 6/19/19 2:49 PM, Tom Lane wrote:
Brent Bates writes:
I tried putting the pg_hba.conf back to stock defaults and that didn't
help any. Here is a snippet of the current file:
# TYPE DATABASEUSERADDRESS METHOD
# "local" is for Uni
Brent Bates writes:
> I tried putting the pg_hba.conf back to stock defaults and that didn't
> help any. Here is a snippet of the current file:
> # TYPE DATABASEUSERADDRESS METHOD
> # "local" is for Unix domain socket connections only
>
I tried putting the pg_hba.conf back to stock defaults and that didn't
help any. Here is a snippet of the current file:
# TYPE DATABASEUSERADDRESS METHOD
# "local" is for Unix domain socket connections only
local all
Brent Bates writes:
> This is a first time install of PostgreSQL version 11.3 on a CentOS
> server running release 7.6.1810. I've just finished setting up the
> postgresql.conf and pg_hba.conf files and am trying to start up PostgreSQL
> for the first time. I'm getting errors no matter w
I've done a lot of Google searching and PostgreSQL archive searching and
can't seem to figure out why I'm having problems.
This is a first time install of PostgreSQL version 11.3 on a CentOS server
running release 7.6.1810. I've just finished setting up the postgresql.conf
and pg_hba
Hi guys,
i am struggling with a problem due, sometime, to a double concurrent update on
the same row of a table.
Since the client application cannot be control, i need to manage - in order to
avoid this situation - the lock of a record due to two updates at the same time.
Is there way to force
Hello
have you tried the same with logical replication in postgresql >= 10?
On 16/6/19 11:45 μ.μ., Torsten Förtsch wrote:
Hi,
out of curiosity I created the following setup, all with 9.6 and pglogical.
D1 is configured as provider with a replication set that contains only 1 table.
Only inser
12 matches
Mail list logo
