Обсуждение: [GENERAL] mild modification to pg_dump
I would need to do a mild change to pg_dump, working against a 9.4 server on linux. Which source tree do I need? Have gcc 4.9.2 in my Lubuntu installation. TIA -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
On Fri, Nov 17, 2017 at 7:51 AM, marcelo <marcelo.nicolet@gmail.com> wrote:
I would need to do a mild change to pg_dump, working against a 9.4 server on linux.
Which source tree do I need? Have gcc 4.9.2 in my Lubuntu installation.
TIA
What exactly do you need to change? Most likely, there is a quick and easy fix for whatever you're doing without modifying pg_dump itself.
That being said, if you really want to modify the source, download the source tarball: https://www.postgresql.org/ftp/source/
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Sorry, I was not exact.
I don't need nor like to change pg_dump. Rather, based on pg_dump code, I need to develop a daemon which can receive a TCP message (from a privileged app) containing some elements: the database to dump, the user under which do that, and his password. (My apps are using that same data, of course, encripted to the common users).
Thank you, Scott.
I don't need nor like to change pg_dump. Rather, based on pg_dump code, I need to develop a daemon which can receive a TCP message (from a privileged app) containing some elements: the database to dump, the user under which do that, and his password. (My apps are using that same data, of course, encripted to the common users).
Thank you, Scott.
On 17/11/17 10:49, Scott Mead wrote:
On Fri, Nov 17, 2017 at 7:51 AM, marcelo <marcelo.nicolet@gmail.com> wrote:I would need to do a mild change to pg_dump, working against a 9.4 server on linux.
Which source tree do I need? Have gcc 4.9.2 in my Lubuntu installation.
TIAWhat exactly do you need to change? Most likely, there is a quick and easy fix for whatever you're doing without modifying pg_dump itself.That being said, if you really want to modify the source, download the source tarball: https://www.postgresql.org/ftp/source/
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general --
On 11/17/2017 12:19 PM, marcelo wrote: > Sorry, I was not exact. > I don't need nor like to change pg_dump. Rather, based on pg_dump > code, I need to develop a daemon which can receive a TCP message (from > a privileged app) containing some elements: the database to dump, the > user under which do that, and his password. (My apps are using that > same data, of course, encripted to the common users). I would just fork pg_dump to do the actual dump rather than try and incorporate its source code into your app. -- john r pierce, recycling bits in santa cruz -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
On 11/17/2017 02:23 PM, John R Pierce wrote: > On 11/17/2017 12:19 PM, marcelo wrote: >> Sorry, I was not exact. >> I don't need nor like to change pg_dump. Rather, based on pg_dump code, I >> need to develop a daemon which can receive a TCP message (from a >> privileged app) containing some elements: the database to dump, the user >> under which do that, and his password. (My apps are using that same data, >> of course, encripted to the common users). > > > I would just fork pg_dump to do the actual dump rather than try and > incorporate its source code into your app. > Specifically, do you mean to write a simple daemon which forks pg_dump at the appropriate time? -- World Peace Through Nuclear Pacification -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
I need to "emulate" the pg_dump code because the password prompt. Years ago I write a program (for the QnX environment) that catched some prompt and emulates the standard input. I don't like to do that again. On 17/11/17 17:23, John R Pierce wrote: > On 11/17/2017 12:19 PM, marcelo wrote: >> Sorry, I was not exact. >> I don't need nor like to change pg_dump. Rather, based on pg_dump >> code, I need to develop a daemon which can receive a TCP message >> (from a privileged app) containing some elements: the database to >> dump, the user under which do that, and his password. (My apps are >> using that same data, of course, encripted to the common users). > > > I would just fork pg_dump to do the actual dump rather than try and > incorporate its source code into your app. > > -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
pg_dump is a libpq client, and thus will read the environment for a variable with the password. no need to emulte any command prompt tty operations.
On Fri, Nov 17, 2017 at 4:06 PM, marcelo <marcelo.nicolet@gmail.com> wrote:
I need to "emulate" the pg_dump code because the password prompt. Years ago I write a program (for the QnX environment) that catched some prompt and emulates the standard input. I don't like to do that again.
On 17/11/17 17:23, John R Pierce wrote:On 11/17/2017 12:19 PM, marcelo wrote:Sorry, I was not exact.
I don't need nor like to change pg_dump. Rather, based on pg_dump code, I need to develop a daemon which can receive a TCP message (from a privileged app) containing some elements: the database to dump, the user under which do that, and his password. (My apps are using that same data, of course, encripted to the common users).
I would just fork pg_dump to do the actual dump rather than try and incorporate its source code into your app.
--Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
I will give expect a try. But the source code embedded in my daemon. On 17/11/17 17:49, Ron Johnson wrote: > On 11/17/2017 02:23 PM, John R Pierce wrote: >> On 11/17/2017 12:19 PM, marcelo wrote: >>> Sorry, I was not exact. >>> I don't need nor like to change pg_dump. Rather, based on pg_dump >>> code, I need to develop a daemon which can receive a TCP message >>> (from a privileged app) containing some elements: the database to >>> dump, the user under which do that, and his password. (My apps are >>> using that same data, of course, encripted to the common users). >> >> >> I would just fork pg_dump to do the actual dump rather than try and >> incorporate its source code into your app. >> > > Specifically, do you mean to write a simple daemon which forks pg_dump > at the appropriate time? > > -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
What about the pgpass file? https://www.postgresql.org/docs/9.2/static/libpq-pgpass.html On 11/17/2017 03:06 PM, marcelo wrote: > I need to "emulate" the pg_dump code because the password prompt. Years > ago I write a program (for the QnX environment) that catched some prompt > and emulates the standard input. I don't like to do that again. > > On 17/11/17 17:23, John R Pierce wrote: >> On 11/17/2017 12:19 PM, marcelo wrote: >>> Sorry, I was not exact. >>> I don't need nor like to change pg_dump. Rather, based on pg_dump code, >>> I need to develop a daemon which can receive a TCP message (from a >>> privileged app) containing some elements: the database to dump, the user >>> under which do that, and his password. (My apps are using that same >>> data, of course, encripted to the common users). >> >> >> I would just fork pg_dump to do the actual dump rather than try and >> incorporate its source code into your app. >> > -- World Peace Through Nuclear Pacification -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
On Fri, Nov 17, 2017 at 4:06 PM, marcelo <marcelo.nicolet@gmail.com> wrote:
I need to "emulate" the pg_dump code because the password prompt. Years ago I write a program (for the QnX environment) that catched some prompt and emulates the standard input. I don't like to do that again.
pg_dump can use an environment variable "PGPASSWORD" upon execution (actually, all libpq programs can). You could have a wrapper that sets the environment variable and then executes pg_dump, this would get you around that prompt. Similarly, you could use the .pgpass file.
--Scott
On 17/11/17 17:23, John R Pierce wrote:On 11/17/2017 12:19 PM, marcelo wrote:Sorry, I was not exact.
I don't need nor like to change pg_dump. Rather, based on pg_dump code, I need to develop a daemon which can receive a TCP message (from a privileged app) containing some elements: the database to dump, the user under which do that, and his password. (My apps are using that same data, of course, encripted to the common users).
I would just fork pg_dump to do the actual dump rather than try and incorporate its source code into your app.
--Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Thank you, Scott.
That's happening me because incomplete docs reading.
Truly, I'm catched in a very big app, so I have no time to read all the docs.
That's happening me because incomplete docs reading.
Truly, I'm catched in a very big app, so I have no time to read all the docs.
On 17/11/17 18:31, Scott Mead wrote:
On Fri, Nov 17, 2017 at 4:06 PM, marcelo <marcelo.nicolet@gmail.com> wrote:I need to "emulate" the pg_dump code because the password prompt. Years ago I write a program (for the QnX environment) that catched some prompt and emulates the standard input. I don't like to do that again.pg_dump can use an environment variable "PGPASSWORD" upon execution (actually, all libpq programs can). You could have a wrapper that sets the environment variable and then executes pg_dump, this would get you around that prompt. Similarly, you could use the .pgpass file.--Scott
On 17/11/17 17:23, John R Pierce wrote:On 11/17/2017 12:19 PM, marcelo wrote:Sorry, I was not exact.
I don't need nor like to change pg_dump. Rather, based on pg_dump code, I need to develop a daemon which can receive a TCP message (from a privileged app) containing some elements: the database to dump, the user under which do that, and his password. (My apps are using that same data, of course, encripted to the common users).
I would just fork pg_dump to do the actual dump rather than try and incorporate its source code into your app.
--Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general --
Again: knowing of .pgpass (thank you Scott) this is what I will do. On 17/11/17 17:49, Ron Johnson wrote: > On 11/17/2017 02:23 PM, John R Pierce wrote: >> On 11/17/2017 12:19 PM, marcelo wrote: >>> Sorry, I was not exact. >>> I don't need nor like to change pg_dump. Rather, based on pg_dump >>> code, I need to develop a daemon which can receive a TCP message >>> (from a privileged app) containing some elements: the database to >>> dump, the user under which do that, and his password. (My apps are >>> using that same data, of course, encripted to the common users). >> >> >> I would just fork pg_dump to do the actual dump rather than try and >> incorporate its source code into your app. >> > > Specifically, do you mean to write a simple daemon which forks pg_dump > at the appropriate time? > > -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
On 2017-11-17 18:56:45 -0300, marcelo wrote: > Truly, I'm catched in a very big app, so I have no time to read all > the docs. People on this list also have jobs. - Andres -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
On Fri, Nov 17, 2017 at 3:58 PM, marcelo <marcelo.nicolet@gmail.com> wrote:
Again: knowing of .pgpass (thank you Scott) this is what I will do.
Just in case you might not know. The perms of the .pgpass file need to not have group or all write access. For instance:
chmod 0600 .pgpass
-m