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 - 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 #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 - 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> Pggraph - Feature #4926 (New): insert/update/deletehttps://public.commandprompt.com/issues/49262007-08-20T16:15:10Zbford -bford@foo.bar
<p>We have the ability to see which relations did what type of dml for a given interval. However we don't have the ability to see that data database wide. What I would to see is on the database graph to have the option to select DML which would sum the n_tup_ins, n_tup_del and n_tup_update for all relations on the particular database and graph it based on the interval.</p> PL/php - Feature #4984 (In Progress): Composite Type Argument as tablehttps://public.commandprompt.com/issues/49842005-12-15T03:38:44Zbford -bford@foo.bar
<p>creating composite type argument named table:</p>
<pre> CREATE TABLE employee (name text, basesalary integer, bonus integer); </pre>
<pre> CREATE TABLE employee_ext (name text, basesalary integer, bonus integer, other text); </pre><br /><pre>
CREATE FUNCTION empcomp(table) RETURNS integer AS $$
return $argsr0['basesalary'] + $argsr0['bonus'];
$$ LANGUAGE 'plphp';
</pre><br />SELECT name, empcomp(table) FROM employee;<br />SELECT name, empcomp(table) FROM employee_ext;
<p>eg. type table is table taken from FROM (so once time will be employee, second time employee_ext)<br />now i must have x functions to do same thing with different argument</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> PL/php - Bug #4972 (In Progress): array PHP <-> Pg conversion is brokenhttps://public.commandprompt.com/issues/49722005-11-23T11:48:44ZÁlvaro Herreraalvherre@commandprompt.com
<p>Element parsing in arrays can easily be confused. Test case:</p>
<pre>
create or replace function another_text_test(text[], int)
returns text language plphp as $$ return $argsr0[$argsr1]; $$;
</pre>
<p>Strings should be quoted before passing them to PHP, so the NOTICE from PHP here is bogus:</p>
<pre>
pl_regression=# select another_text_test($${"foo",'bar', "{"}$$, 0);
NOTICE: plphp: Use of undefined constant foo - assumed 'foo'
another_text_test
-------------------
foo
(1 fila)
</pre>
<p>The same reason causes this to "eat" the inner level of quotes:</p>
<pre>
pl_regression=# select another_text_test($${"'bar'", "{"}$$, 0);
another_text_test
-------------------
bar
(1 fila)
</pre>
<p>Note particularly this totally unexpected behavior:</p>
<pre>
pl_regression=# select another_text_test($${"'bar'", "{"}$$, 1);
another_text_test
-------------------
array(
(1 fila)
</pre> PL/php - Feature #4967 (In Progress): Redesign memory handlinghttps://public.commandprompt.com/issues/49672005-11-16T17:31:06ZÁlvaro Herreraalvherre@commandprompt.com
<p>Currently memory is not handled very well. It would be nice if we had one MemoryContext for each function that could be automatically reset or deleted when the function is recompiled. Additionally we would need a compilation context, and maybe an execution context as well.</p>