public.commandprompt.com: Issueshttps://public.commandprompt.com/https://public.commandprompt.com/favicon.ico?16484970162012-09-17T04:13:45Zpublic.commandprompt.com
Redmine pitrtools - 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 #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> 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> Pggraph - Bug #4958 (New): Fix the "Help I have no data" problem with pggraph.https://public.commandprompt.com/issues/49582008-07-25T11:37:31ZAurynn Shawashaw@commandprompt.com
<p>Make a moving window when trying to establish the datnames &c in the tables.</p> Pggraph - Bug #4956 (New): dbrollup.py needs to support pggraph 2.2https://public.commandprompt.com/issues/49562008-07-25T08:02:24ZAurynn Shawashaw@commandprompt.com
<p>Per <a class="issue tracker-1 status-5 priority-5 priority-high3 closed" title="Bug: 1-hour bug broken on v2.2 installs (Closed)" href="https://public.commandprompt.com/issues/4953">#4953</a> and the 1-hour bug, dbrollup.py needs to be updated for pggraph 2.2 to support the new table, table structure, and different location of the pggraph_clients data.</p> Pggraph - Bug #4952 (New): Help interfacehttps://public.commandprompt.com/issues/49522008-07-21T10:40:30ZAurynn Shawashaw@commandprompt.com
<p>Come up with a mechanism to provide "help" tooltips as needed for various form elements. Decouple from existing templates and code, figure out a mechanism/library to handle it.</p> Pggraph - Bug #4951 (New): Document date range behaviourhttps://public.commandprompt.com/issues/49512008-07-21T10:38:00ZAurynn Shawashaw@commandprompt.com
<p>As title - document how pggraph will function in Date Range mode, as well as out of Date Range mode.</p> Pggraph - Bug #4949 (New): Document behaviourhttps://public.commandprompt.com/issues/49492008-07-17T16:59:08ZAurynn Shawashaw@commandprompt.com
<p>When date start and date end are used, it defaults to the range behavior.</p>
<p>When neither are selected, it defaults to the previous behavior, which is now() - interval time.</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 #4945 (New): Force all graphs to abort if non-specific data specifiedhttps://public.commandprompt.com/issues/49452008-07-15T15:32:45ZAurynn Shawashaw@commandprompt.com
<p>For all graphs, prevent date ranges from working if:</p>
<ul>
<li>High-level, multi-graph pages would be generated normally</li>
<li>Non-specific data is passed to the graphing function.
<ul>
<li>For pggraph_database, it REQUIRES a datname</li>
<li>For pggraph_table, it requires a datname, a tablename and a schemaname</li>
<li>For pggraph_index, it requires a datname, an indexname, and a schemaname</li>
</ul></li>
</ul> Pggraph - Bug #4937 (New): Modification of DB Client code for date rangeshttps://public.commandprompt.com/issues/49372008-07-14T10:45:13ZAurynn Shawashaw@commandprompt.com
<p>The client code needs to be modified to take advantage of the new date range function signatures.</p>
<p>This will require:</p>
<ul>
<li>Modification of the functions that call the DB functions.
<ul>
<li>Ideally (and this will be a new ticket) I'd like to write the transparent python->db function mapper (obj.func(arg,arg) gets seamlessly converted to SELECT * FROM func(arg,arg))</li>
</ul></li>
</ul> 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>