Re: logical replication - negative bitmapset member not allowed

On 04/04/2019 22:37, Peter Intrauterine wrote: > On 2019-04-01 23:43, Alvaro Herrera wrote: >> Maybe the replica identity of a table got set to a unique index on oid? >> Or something else involving system columns? (If replication is >> otherwise working, the I suppose there's a separate publicatio

Re: Seeded Replication

On 2019-04-03 13:44, Lou Tseng wrote: > However, our database is about 200G and it will take a long time to > complete the initial data copy.  We would like to manually seed the > subscriber database with data dump and then turn on the subscription > like depesz showed in this > post  > https://www

Re: logical replication - negative bitmapset member not allowed

On 2019-04-01 23:43, Alvaro Herrera wrote: > Maybe the replica identity of a table got set to a unique index on oid? > Or something else involving system columns? (If replication is > otherwise working, the I suppose there's a separate publication that's > having the error; the first thing to isol

Re: CVE-2019-9193 about COPY FROM/TO PROGRAM

Hi On 2019-04-04 21:50:41 +0200, Magnus Hagander wrote: > On Thu, Apr 4, 2019 at 9:45 PM Tom Lane wrote: > > > Jeremy Schneider writes: > > > I'm all for having clear documentation about the security model in > > > PostgreSQL, but I personally wouldn't be in favor of adding extra > > > wording

RE: Recommendation to run vacuum FULL in parallel

From: Perumal Raj So conclude the requirement here , The only way to parallelism is multiple script. And no need to do REINDEX exclusively. Question : Do we need to consider Table dependencies while preparing script in order to avoid table locks during vacuum full ? We have a small bash scrip

Re: CVE-2019-9193 about COPY FROM/TO PROGRAM

On Thu, Apr 4, 2019 at 9:45 PM Tom Lane wrote: > Jeremy Schneider writes: > > I'm all for having clear documentation about the security model in > > PostgreSQL, but I personally wouldn't be in favor of adding extra > > wording to the docs just to pacify concerns about a CVE which may have > > be

Re: CVE-2019-9193 about COPY FROM/TO PROGRAM

Jeremy Schneider writes: > I'm all for having clear documentation about the security model in > PostgreSQL, but I personally wouldn't be in favor of adding extra > wording to the docs just to pacify concerns about a CVE which may have > been erroneously granted by an assigning authority, who possi

Re: How serial primary key numbers are assigned

On 4/4/19 11:27 AM, Rich Shepard wrote: On Thu, 4 Apr 2019, Adrian Klaver wrote: See: https://www.postgresql.org/docs/11/sql-createsequence.html Thanks, Adrian. My web searches did not find this URL, only results on how to set up automatic serial id generation. Well serial is basically a m

Re: How serial primary key numbers are assigned

On Thu, 4 Apr 2019, Adrian Klaver wrote: See: https://www.postgresql.org/docs/11/sql-createsequence.html Thanks, Adrian. My web searches did not find this URL, only results on how to set up automatic serial id generation. Regards, Rich

Re: How serial primary key numbers are assigned

On 4/4/19 11:04 AM, Rich Shepard wrote: Just out of curiosity, how does postgres assign serial primary key identifiers when rows are inserted in multiple, separate working sessions? I'm populating tables using INSERT INTO statements in separate working sessions and see that the assigned id numbe

How serial primary key numbers are assigned

Just out of curiosity, how does postgres assign serial primary key identifiers when rows are inserted in multiple, separate working sessions? I'm populating tables using INSERT INTO statements in separate working sessions and see that the assigned id numbers are sequential in each session, but ha

Re: stale WAL files?

> On Apr 3, 2019, at 5:23 PM, Rene Romero Benavides > wrote: > > > > On Wed, Apr 3, 2019 at 1:05 PM Rob Sargent > wrote: > > >> On Apr 1, 2019, at 9:20 PM, Rene Romero Benavides > > wrote: >> >> >> On Mon, Apr 1, 2019 at 6:30

Re: dbuser acess privileges

Durgamahesh Manne writes: > On Thu, Apr 4, 2019 at 5:55 PM Patrick FICHE > wrote: >> If I’m not wrong, UPDATE requires SELECT permission as the UPDATE >> statement needs to read the data to be updated. > in 9.3 versionGrant access on update command is worked EVEN I DID NOT > EXECUTE THIS

Re: PostgreSQL Windows 2019 support ?

On Thu, 4 Apr 2019 at 22:15, david moloney wrote: > Windows 2019 isn’t listed as a supported platform on > https://www.postgresql.org/download/windows/ > > I’m presuming there’s a qualification process before it’s listed here ? Is > this in progress ? That process is having a buildfarm member

Re: dbuser acess privileges

*From:* Durgamahesh Manne *Sent:* Thursday, April 4, 2019 12:07 PM *To:* pgsql-general@lists.postgresql.org *Subject:* dbuser acess privileges hi Respected international pgsql team pershing=# grant INSERT on public.hyd to ravi; GRANT i have granted insert command access to non superuser

RE: dbuser acess privileges

Here is the extract of documentation relative to GRANT UPDATE UPDATE Allows UPDATE of any column, or the specific columns listed, of the specified table. (In practice, any nontrivial UPDATE command will require SELECT privilege as well, si

Re: dbuser acess privileges

You'd think the implicit SELECT perm of that table for the explicit use of UPDATE would be covered by GRANT UPDATE. On 4/4/19 7:25 AM, Patrick FICHE wrote: Hi, If I’m not wrong, UPDATE requires SELECT permission as the UPDATE statement needs to read the data to be updated. So, you should p

RE: dbuser acess privileges

Hi, If I’m not wrong, UPDATE requires SELECT permission as the UPDATE statement needs to read the data to be updated. So, you should probably add GRANT SELECT and you get it work. Regards, Patrick Fiche Database Engineer, Aqsacom Sas. c. 33 6 82 80 69 96 [01-03_AQSA_Main_Corporate_Logo_JPEG_Wh

Re: dbuser acess privileges

On Thu, Apr 4, 2019 at 4:14 PM Durgamahesh Manne wrote: > > > > On Thu, Apr 4, 2019 at 3:55 PM Ron wrote: > >> On 4/4/19 5:07 AM, Durgamahesh Manne wrote: >> > hi >> > Respected international pgsql team >> > >> > pershing=# grant INSERT on public.hyd to ravi; >> > GRANT >> > i have granted inser

Re: dbuser acess privileges

On Thu, Apr 4, 2019 at 3:55 PM Ron wrote: > On 4/4/19 5:07 AM, Durgamahesh Manne wrote: > > hi > > Respected international pgsql team > > > > pershing=# grant INSERT on public.hyd to ravi; > > GRANT > > i have granted insert command access to non superuser(ravi) > > pershing=> insert into hyd (id

Re: dbuser acess privileges

On 4/4/19 5:07 AM, Durgamahesh Manne wrote: hi Respected international pgsql team pershing=# grant INSERT on public.hyd to ravi; GRANT i have granted insert command access to non superuser(ravi) pershing=> insert into hyd (id,name) values('2','delhi'); INSERT 0 1 here data inserted pershing=#

dbuser acess privileges

hi Respected international pgsql team pershing=# grant INSERT on public.hyd to ravi; GRANT i have granted insert command access to non superuser(ravi) pershing=> insert into hyd (id,name) values('2','delhi'); INSERT 0 1 here data inserted pershing=# grant UPDATE on public.hyd to ravi; GRANT i h

Re: PostgreSQL Windows 2019 support ?

Hi, Correct – I am talking about Windows Server 2019 which has been re-released since January 2019. Windows 2019 isn’t listed as a supported platform on https://www.postgresql.org/download/windows/ I’m presuming there’s a qualification process before it’s listed here ? Is this in progress ?