public.commandprompt.com: Issueshttps://public.commandprompt.com/https://public.commandprompt.com/favicon.ico?16484970162014-05-11T09:24:00Zpublic.commandprompt.com
Redmine postgres_fdw - Bug #5303 (New): [SPAM] Good shoes good priceshttps://public.commandprompt.com/issues/53032014-05-11T09:24:00ZAlvherre -dntnmh@dng.vnn.vnpitrtools - 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> PL/php - Feature #5259 (New): Add support for anonymous DO blocks.https://public.commandprompt.com/issues/52592011-05-27T05:52:31ZAlexey Klyukinalexk@commandprompt.com
<p>PostgreSQL 9.0 introduced a notion of inline DO blocks:<br /><a class="external" href="http://www.postgresql.org/docs/9.0/interactive/sql-do.html">http://www.postgresql.org/docs/9.0/interactive/sql-do.html</a></p>
<p>So far, nothing stops us from adding support for such blocks written in PL/PHP.</p> PL/php - Bug #5258 (New): Get rid of the trusted PL/PHPhttps://public.commandprompt.com/issues/52582011-05-27T05:43:07ZAlexey Klyukinalexk@commandprompt.com
<p>Apparently, the trusted PL/PHP has lots of security problems due to its trusted status, from sharing the same interpreter with an untrusted one, to <br />the fact that the trusted implementation relies on PHP safe mode, which is deprecated and allows some 'untrusted' (in PG's sense) operations, i.e. filesystem/network access. ATM we need to get rid of PL/PHP and leave only PL/PHPU implementation.</p> PL/php - Bug #5255 (New): support TRUNCATE triggershttps://public.commandprompt.com/issues/52552011-05-21T16:29:20ZÁlvaro Herreraalvherre@commandprompt.com
<p>$SUBJECT</p> PL/php - Bug #5225 (New): Unable to build PL/php on OS X (PHP 5.3)https://public.commandprompt.com/issues/52252010-06-29T05:25:59ZAlexey Klyukinalexk@commandprompt.com
<p>On OS X embed is built as a bundle instead of a library, making it impossible to link against it.</p>
<p>I've submitted the problem to the PHP project:<br /><a class="external" href="http://bugs.php.net/bug.php?id=48318">http://bugs.php.net/bug.php?id=48318</a></p>
<p>Still, it's not possible to build PL/php at the moment on this platform.</p> Pggraph - Bug #4948 (New): in pggraph_table, prevent crash if no tables presenthttps://public.commandprompt.com/issues/49482008-07-16T21:42:46ZAurynn Shawashaw@commandprompt.com
<p>If a given database doesn't have any tables, and it is the default in pggraph_table.py, then we need to catch that and switch to a different database/datname.</p> Pggraph - Bug #4947 (New): Do testing of data arrayshttps://public.commandprompt.com/issues/49472008-07-16T21:01:03ZAurynn Shawashaw@commandprompt.com
<p>While generating date range pages, we should test the length of each return set, so that we can trim out offsets that are going to be no-shows.</p>
<p>This is going to be kind of expensive to do for every page refresh, but I feel it's <br />worthwhile.</p>
<p>Alternatively, just have "NO DATA" splayed over the image in the event that there's no data.</p>
<p>How should we approach this?</p> Pggraph - Bug #4943 (New): Future Planning and Ideashttps://public.commandprompt.com/issues/49432008-07-14T11:32:17ZAurynn Shawashaw@commandprompt.com
<ul>
<li>Javascript+SVG-based graphs, based on example code Darcy showed off a while back. This would allow us to do offset-based graphs (clicking an offset of, say, 5 days scrolls it back in time that far), as well as the ability to do click & drag ala the Google Maps interface.</li>
</ul> Pggraph - Bug #4940 (New): Remove prefixeshttps://public.commandprompt.com/issues/49402008-07-14T11:05:46ZAurynn Shawashaw@commandprompt.com
<p>As we are moving to a schema'd design, remove the prefix additions from the code and all new installations.</p>
<p>This involves a plpgsql function signature change.</p> Pggraph - Bug #4936 (New): Modify averaging functionshttps://public.commandprompt.com/issues/49362008-07-14T10:11:55ZAurynn Shawashaw@commandprompt.com
<p>All plpgsql functions will need two new arguments, and one removed argument:</p>
<p>start DATE, end DATE, and removal of offset INT.</p>
<p>The functions will be altered in the following ways:</p>
<ul>
<li>Determining the length of the WHILE loop from the date ranges, if present, instead of using the interval to calculate it.</li>
<li>Alter the queries to use the start DATE parameter to position the start of the set, and then utilize the WHILE loop to offset from that point, ie, WHERE date = date_start + (interval * iterations)::interval</li>
</ul> Pggraph - Feature #4933 (New): Feature requests, pggraphhttps://public.commandprompt.com/issues/49332008-03-12T12:44:15ZAurynn Shawashaw@commandprompt.com
<p>From cashnet:</p>
<pre>
Should at least display timezone on graphs (would be better if this was configurable).
Unused indexes is too strict, assuming that it's just looking for 0 idxscans (since it's not showing that, I don't know... :) ). It should show index usage stats, and also include indexes that have low usage, perhaps compared to other indexes on the table, or to table stats.
It'd also be good to have a report of tables that could use indexes. I'll typically use a metric like tablescans * relpages, with a cap of say 100 or 200. If this was done with stats over time the metric would essentially be "here's tables that we're doing more than X sequential pages per $unit_time".
</pre> Pggraph - Feature #4932 (New): Have pggraph directly access Wiki passwordshttps://public.commandprompt.com/issues/49322007-12-31T10:28:34ZAurynn Shawashaw@commandprompt.com
<p>Should we have pggraph be on its own, independent password auth, or link it directly to the wiki pw auth?</p>