public.commandprompt.com: Issueshttps://public.commandprompt.com/https://public.commandprompt.com/favicon.ico?16484970162017-08-02T23:44:00Zpublic.commandprompt.com
Redmine postgresql-snap - Task #5340 (New): Change package namehttps://public.commandprompt.com/issues/53402017-08-02T23:44:00ZIvan Lezhnjov
<p>We need to change the name of the snap packages from Postgresql to Postgres.</p> postgresql-snap - Task #5339 (New): Explore tracks featurehttps://public.commandprompt.com/issues/53392017-06-09T03:47:00ZIvan Lezhnjov
<p>While working on <a class="issue tracker-4 status-3 priority-4 priority-default closed" title="Task: Explore app alias functionality (Resolved)" href="https://public.commandprompt.com/issues/5338">#5338</a> (Explore app alias functionality), I was asked in snapcraft forum if we had any plans to support tracks instead of using version number in a package name.</p>
<p>On a quick look, tracks seems like a central feature of snap's package management design and we most likely will have to start using it.</p>
<p>Essentially, it is a way to catalog software using the following scheme track/risk/branch.</p>
<p>E.g. 9.3/stable/psql-freeze-fix</p>
<p>I will make some tests to get a good idea about how it works, how we could transition from the current approach and start using tracks.</p>
<p>Ivan</p> postgresql-snap - Bug #5331 (New): PgBackResthttps://public.commandprompt.com/issues/53312017-02-10T09:56:05ZJoshua Drake
<p>It is time to add PgBackRest to the repository.</p>
<p>JD<br />-- <br />Command Prompt, Inc. <a class="external" href="http://the.postgres.company/">http://the.postgres.company/</a><br /> +1-503-667-4564<br />PostgreSQL Centered full stack support, consulting and development.<br />Everyone appreciates your honesty, until you are honest with them.<br />Unless otherwise stated, opinions are my own.</p> postgresql-snap - Feature #5327 (In Progress): New snap packages to be createdhttps://public.commandprompt.com/issues/53272016-12-09T07:11:35ZJoshua Drake
<p>pgbouncer<br />pgpool</p> postgresql-snap - Task #5321 (New): Make postgres a systemd daemonhttps://public.commandprompt.com/issues/53212016-10-28T06:34:00ZIvan Lezhnjov
<p>Running postgres process as a daemon via an automatically generated systemd service file, results in snap utility failing to install a snap package.</p>
<p>The reason for this is because the said snap utility attempts to start all daemons when it is installing a snap package. The package is always installed as root and thus any daemon is run as root too. However, PostgreSQL is not designed to run as root and it actually refuses to. Thus, if a daemon startup fails, installation of a snap package fails too.</p>
<p>Ideally, postgres should be a systemd-managed process but given the clash of design philosophies it currently doesn't work well.</p>
<p>We need to start a dialog with snapcraft developers and see if they can propose a solution to this problem that doesn't involve patching PostgreSQL.</p> postgres_fdw - Bug #5301 (New): My husband loves Jacob & Cohttps://public.commandprompt.com/issues/53012014-05-08T03:17:20ZPostgres fdwgettu@fenwickkeats.compostgres_fdw - Bug #5292 (New): [SPAM] Good shoes good priceshttps://public.commandprompt.com/issues/52922014-04-11T14:06:06ZLadyregina -apei@cat-atelierduchateau.compostgres_fdw - Bug #5291 (New): Great watches at cut-priceshttps://public.commandprompt.com/issues/52912014-04-11T07:30:00ZJkawasaki -info@atlaspersia.compitrtools - Feature #5265 (New): Avoid the need to manually edit postgresql.conf fileshttps://public.commandprompt.com/issues/52652012-09-17T04:13:45ZAlexey Klyukinalexk@commandprompt.com
<p>Right now, we have a bizarre combination of running cmd_archiver from the command line and plugging it in postgresql.conf manually. Given that we already know the location of postgresql.conf, we can edit it to set all necessary options (wal_level, max_wal_senders, archive_mode, archive_command) automatically, leaving only database restart as a task that should be performed manually.</p> pitrtools - Discussion #5263 (New): PITRTools ini configuration files are too complexhttps://public.commandprompt.com/issues/52632012-09-17T04:03:52ZAlexey Klyukinalexk@commandprompt.com
<p>Since we position PITRTools as a tool to simplify WAL-shipping and replication setup, I though I'd count the number of options once needs to set in PIRTools, against pristine PostgresSQL:</p>
<p>PITRTools:<br />Archiver: 15<br />Standby: 31.</p>
<p>Comparing to the pristine PostgreSQL:<br />primary: (wal_level, archive_mode, archive_command, max_wal_senders) - 4.</p>
<p>standby (most of them belong to recovery.conf): (hot_standby, standby_mode, primary_conninfo, restore_command, archive_cleanup_command): 5</p>
<p>We need to rethink PITRTools configuration options. I've made the first step by splitting them into required and uncommon, and put reasonable defaults for the second ones (i.e. assumed ssh and rsync path is fixed, and there is no need to tweak rsync options or set ssh_debug), but to make the tool easier than pristine PostgreSQL we need to put some code to autodetect some of the parameters (i.e. autodetect things like PostgreSQL version, checkpoint_segments value for 8.2 and below, rsync_version, etc.)</p> PL/php - Bug #5260 (New): The function could not return varchar string -- When there is function ...https://public.commandprompt.com/issues/52602011-11-02T23:16:35Zanthony chenzhihong.chen.cn@gmail.com
<p>There is pl/php definition as attached plsimple.sql. Which include other files blank.php.</p>
<p>Run first time:<br />test=# select plsimple();<br /> plsimple<br />----------</p>
<p>(1 row)</p>
<p>test=#<br />Run second time:<br />test=# select plsimple();<br /> plsimple<br />--------------<br /> Hello world!<br />(1 row)</p>
<p>When remove the definition of function test() in the blank.php, the issue disppears.</p> postgres.js - Support #5257 (New): method to catch error on connection?https://public.commandprompt.com/issues/52572011-05-26T09:15:50ZRick Hardingrharding@mitechie.com
<p>I'm trying to figure out how to properly catch an exception such as when the db server is unavailable. I've tried binding to a connection.on('error') event, but it doesn't look like it emits one. I see 'error' emitted when a query fails, but nothing on the actual connection attempt. Am I missing the proper way to handle that?</p>
<p>Thanks</p> Simpycity - Bug #5000 (New): Automatic Rollback Fix.https://public.commandprompt.com/issues/50002009-04-29T11:22:37ZLacey Powerslacey.powers@commandprompt.com
<p>Simpycity doesn't always issue a rollback for some transactions, such as failed functions.</p>
<p>This should be fixed, and an appropriate test case created to verify the fix and test in future releases.</p> Simpycity - Bug #4993 (New): Finish docshttps://public.commandprompt.com/issues/49932008-11-25T11:31:41ZAurynn Shawashaw@commandprompt.com
<p>Finish docs</p> PL/php - Feature #4979 (In Progress): Add support for IN/OUT parametershttps://public.commandprompt.com/issues/49792005-12-05T07:37:14ZÁlvaro Herreraalvherre@commandprompt.com
<p>Add support for OUT parameters so that the user can skip specifying a return type explicitely.</p>