Re: [GENERAL] pg_dumping extensions having sequences with 9.6beta3

Michael, * Michael Paquier (michael.paqu...@gmail.com) wrote: > On Tue, Jul 26, 2016 at 4:50 PM, Noah Misch wrote: > > [Action required within 72 hours. This is a generic notification.] > > > > The above-described topic is currently a PostgreSQL 9.6 open item. Stephen, > >

Re: [GENERAL] Uber migrated from Postgres to MySQL

-- Sent from mobile. On Jul 26, 2016, at 5:56 PM, Joshua D. Drake wrote: > On 07/26/2016 02:49 PM, Rakesh Kumar wrote: > This is an old news. They are using mysql as a nosql to store schemaless. > Basically one giant blob col. And thats where the role of mysql ends.

Re: [GENERAL] Uber migrated from Postgres to MySQL

On 07/26/2016 02:49 PM, Rakesh Kumar wrote: This is an old news. They are using mysql as a nosql to store schemaless. Basically one giant blob col. And thats where the role of mysql ends. The bulk of the processing will be in nosql. That doesn't mean they didn't bring up some very good

Re: [GENERAL] Uber migrated from Postgres to MySQL

This is an old news. They are using mysql as a nosql to store schemaless. Basically one giant blob col. And thats where the role of mysql ends. The bulk of the processing will be in nosql. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your

Re: [GENERAL] yum repo, pgloader

On 07/26/2016 12:54 PM, John R Pierce wrote: On 7/22/2016 5:50 PM, Adrian Klaver wrote: On 07/22/2016 05:24 PM, John R Pierce wrote: I note that pgloader is in the yum repo for Postgresql 9.2 on Centos 6, but not 9.3, 9.4, 9.5, wondering if there's a reason it was dropped? If I where to

Re: [GENERAL] Weirdness with the stats collector process

Matthew Musgrove writes: > I asked what network changes were made on July 7th around 14:05 and was told > that they disabled IPv6! I had them turn it back on and stats started working > immediately. Ooops ... > I have since changed the config from

Re: [GENERAL] yum repo, pgloader

On 7/22/2016 5:50 PM, Adrian Klaver wrote: On 07/22/2016 05:24 PM, John R Pierce wrote: I note that pgloader is in the yum repo for Postgresql 9.2 on Centos 6, but not 9.3, 9.4, 9.5, wondering if there's a reason it was dropped? If I where to hazard a guess it would have to do with pgloader

Re: [GENERAL] question on parsing postgres sql queries

On Tue, Jul 26, 2016 at 3:20 PM, Jerome Wagner wrote: > > Would it make sense to use these sgml synopsis as some kind of source of > truth, parse them, and automatically generate a parser for a specifc > language ? > ​What problem are you trying to solve here?​ to

Re: [GENERAL] question on parsing postgres sql queries

Jerome Wagner writes: > Would it make sense to use these sgml synopsis as some kind of source of > truth, parse them, and automatically generate a parser for a specifc > language ? Probably not. First, it is not uncommon for corner cases (such as legacy syntaxes) to

Re: [GENERAL] Weirdness with the stats collector process

On 07/25/2016 03:20 PM, Tom Lane wrote: Matthew Musgrove writes: One of our instances has been behaving -- oddly. Most queries are blazing fast. It appears to just be some of the stat views that are slow. It sounds like

[GENERAL] question on parsing postgres sql queries

Hello, I am doing some research on postgres sql query parsing. I have found the https://github.com/lfittl/libpg_query project which manages to re-use the native postgres server parser. For using this, you need to accept an external dependency on a lib compiled out of the postgres source. I was

Re: [GENERAL] How to stop script executions

On Tue, Jul 26, 2016 at 7:53 PM, John McKown wrote: > I agree. From my reading at: > https://www.postgresql.org/docs/9.5/static/sql-copy.html the COPY FROM > PROGRAM is only available to a PostgreSQL user who is database superuser. > That, sort of, implies to me

Re: [GENERAL] Uber migrated from Postgres to MySQL

Many comments: https://news.ycombinator.com/item?id=12166585 https://www.reddit.com/r/programming/comments/4uph84/why_uber_engineering_switched_from_postgres_to/ On Tue, Jul 26, 2016 at 7:39 PM, Guyren Howe wrote: > Honestly, I've never heard of anyone doing that. But it

Re: [GENERAL] Uber migrated from Postgres to MySQL

On 07/26/2016 10:39 AM, Guyren Howe wrote: Honestly, I've never heard of anyone doing that. But it sounds like they had good reasons. https://eng.uber.com/mysql-migration/ Thoughts? Hello, I started a thread about hackers on this. Sincerely, JD -- Command Prompt, Inc.

[GENERAL] Uber migrated from Postgres to MySQL

Honestly, I've never heard of anyone doing that. But it sounds like they had good reasons. https://eng.uber.com/mysql-migration/ Thoughts? -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription:

Re: [GENERAL] How to stop script executions

On Tue, Jul 26, 2016 at 7:49 PM, David G. Johnston < david.g.johns...@gmail.com> wrote: > ​For superusers, no. You'd have to protect the system using external > tools to limit what areas and commands the postgres (or whatever PostgreSQL > runs as) user ​can access. > Thanks David for the

Re: [GENERAL] How to stop script executions

On Tue, Jul 26, 2016 at 9:05 AM, Melvin Davidson wrote: > > > On Tue, Jul 26, 2016 at 9:52 AM, Dev Kumkar > wrote: > >> On Tue, Jul 26, 2016 at 6:59 PM, David G. Johnston < >> david.g.johns...@gmail.com> wrote: >> >>> ​Typically this means that

Re: [GENERAL] How to stop script executions

On Tue, Jul 26, 2016 at 9:48 AM, Dev Kumkar wrote: > On Tue, Jul 26, 2016 at 6:54 PM, David G. Johnston < > david.g.johns...@gmail.com> wrote: > >> ​Superuser: yes (specifically I'm thinking the COPY FROM PROGRAM command, >> but also C language functions) >> Ordinary

Re: [GENERAL] How to stop script executions

On Tue, Jul 26, 2016 at 9:52 AM, Dev Kumkar wrote: > On Tue, Jul 26, 2016 at 6:59 PM, David G. Johnston < > david.g.johns...@gmail.com> wrote: > >> ​Typically this means that given user only having psql, or some other >> backend protocol only, connect to the database are

Re: [GENERAL] RE: [GENERAL] Re: [GENERAL] A simple extension immitating pg_notify‏

On 07/25/2016 05:52 PM, Mehran Ziadloo wrote: Sorry if my terminology is not accurate. But by an instance, I mean a PostgreSQL installation. And I call it an instance (and not a database) not to confuse it with the concept of databases (as in databases / schemas). Even when I'm trying to clarify

Re: [GENERAL] How to stop script executions

On Tue, Jul 26, 2016 at 6:59 PM, David G. Johnston < david.g.johns...@gmail.com> wrote: > ​Typically this means that given user only having psql, or some other > backend protocol only, connect to the database are they able to execute > arbitrary commands as the user running the PostgreSQL process

Re: [GENERAL] How to stop script executions

On Tue, Jul 26, 2016 at 6:54 PM, David G. Johnston < david.g.johns...@gmail.com> wrote: > ​Superuser: yes (specifically I'm thinking the COPY FROM PROGRAM command, > but also C language functions) > Ordinary user: not that I can think of. > OK, is there a way to restrict usage of COPY FROM

Re: [GENERAL] How to stop script executions

On Tue, Jul 26, 2016 at 9:21 AM, Sameer Kumar wrote: > >> Yeah these extensions are not present, are their any chances of running >> OS commands from database? >> > > What do you mean by "from database"? I think you need to lay down your > requirement and goal more

Re: [GENERAL] How to stop script executions

On Tue, Jul 26, 2016 at 9:19 AM, Dev Kumkar wrote: > On Tue, Jul 26, 2016 at 6:35 PM, David G. Johnston < > david.g.johns...@gmail.com> wrote: > >> The way to go about prohibiting their usage altogether is specific to >> your installation method. But by default those

Re: [GENERAL] How to stop script executions

On Tue, Jul 26, 2016 at 9:16 AM, Alex Ignatov wrote: > revoke usage on language plpythonu from username; > > revoke usage on language plperl(u) from username; > Actually, the usage permission for an untrusted language appears to be pointless. Only superusers can create

Re: [GENERAL] How to stop script executions

On Tue, 26 Jul 2016, 9:20 p.m. Dev Kumkar, wrote: > On Tue, Jul 26, 2016 at 6:29 PM, Sameer Kumar > wrote: > > You mean you don't want any routines/functions written in Pl/perl or >> PL/pythin to get executed? >> >> If that is what you are

Re: [GENERAL] How to stop script executions

On Tue, Jul 26, 2016 at 6:29 PM, Sameer Kumar wrote: You mean you don't want any routines/functions written in Pl/perl or > PL/pythin to get executed? > > If that is what you are looking for them simply drop the extension for > these languages or deny privilege to

Re: [GENERAL] How to stop script executions

On Tue, Jul 26, 2016 at 6:35 PM, David G. Johnston < david.g.johns...@gmail.com> wrote: > The way to go about prohibiting their usage altogether is specific to your > installation method. But by default those languages are not installed into > newly created databases and only a superuser can

Re: [GENERAL] How to stop script executions

revoke usage on language plpythonu from username; revoke usage on language plperl(u) from username; Alex Ignatov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company On 26.07.2016 16:05, David G. Johnston wrote: On Tue, Jul 26, 2016 at 8:53 AM, Dev Kumkar

Re: [GENERAL] How to stop script executions

On Tue, Jul 26, 2016 at 8:53 AM, Dev Kumkar wrote: > Hello Experts, > > I want to have my postgreSQL database to only execute SQLs and avoid > execution of perl and python script executions. > > Can you please suggest ways to achieve this? > > The way to go about

Re: [GENERAL] How to stop script executions

On Tue, 26 Jul 2016, 8:54 p.m. Dev Kumkar, wrote: > Hello Experts, > > I want to have my postgreSQL database to only execute SQLs and avoid > execution of perl and python script executions. > You mean you don't want any routines/functions written in Pl/perl or PL/pythin

[GENERAL] How to stop script executions

Hello Experts, I want to have my postgreSQL database to only execute SQLs and avoid execution of perl and python script executions. Can you please suggest ways to achieve this? Regards...

[GENERAL] Re: [GENERAL] RE: [GENERAL] Re: [GENERAL] A simple extension immitating pg_notify‏

> On 26 Jul 2016, at 2:52, Mehran Ziadloo wrote: > > Sorry if my terminology is not accurate. But by an instance, I mean a > PostgreSQL > installation. And I call it an instance (and not a database) not to confuse it > with the concept of databases (as in databases /

Re: [GENERAL] pg_dumping extensions having sequences with 9.6beta3

On Tue, Jul 26, 2016 at 4:50 PM, Noah Misch wrote: > [Action required within 72 hours. This is a generic notification.] > > The above-described topic is currently a PostgreSQL 9.6 open item. Stephen, > since you committed the patch believed to have created it, you own this

Re: [GENERAL] pg_dumping extensions having sequences with 9.6beta3

On Sat, Jul 23, 2016 at 01:40:01PM +0900, Michael Paquier wrote: > On Fri, Jul 22, 2016 at 6:27 PM, Philippe BEAUDOIN wrote: > > I am currently playing with extensions. And I found a strange behaviour > > change with 9.6beta2 and 3 when pg_dumping a database with an extension >