time server - Search results in mailing lists
Mailing lists >> pgsql-patches >> Thread
2008-09-15 10:35:53 | Solve a problem of LC_TIME of windows. (Hiroshi Saito)
TIME. In Japanese environment, return value is SJIS(CP932). Then, SJIS(CP932) can't be chosen by SERVER
Mailing lists >> pgsql-patches >> Thread
2008-09-05 16:13:13 | libpq events patch (with sgml docs) (Andrew Chernow)
time to initialize any instanceData + an event procedure may need. Only one register event will be fired per connection. + If the event procedure fails, the registration is aborted. + + + typedef struct + { + const PGconn *conn; + } PGEventRegister; + + When
Mailing lists >> pgsql-patches >> Thread
2008-09-02 05:36:59 | Re: rmgr hooks and contrib/rmgr_hook (Simon Riggs)
server to determine when that is called. Calling code at the time _PG_init() runs
Mailing lists >> pgsql-patches >> Thread >> Search in thread (2)
2008-07-04 08:06:00 | Re: Relation forks & FSM rewrite patches (Simon Riggs)
time. I'm not happy about the FSM being WAL logged for minor changes (new pages, yes). The high number of changes will cause extra traffic where we don't want it. This will accentuate
Mailing lists >> pgsql-patches >> Thread
2008-07-03 10:11:39 | Re: EXPLAIN progress info (Heikki Linnakangas)
server, opening a new connection each time. Any ideas on that? How about a GUC to send
Mailing lists >> pgsql-patches >> Thread
2008-06-25 01:34:10 | Re: [HACKERS] Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout (daveg)
timely way. Please see http:///pgsql-patches/2008-05/msg00351.php for the orginal patch and problem description. A sample failure instance from a very heavy batch environment with a lot of materialized views being maintained concurrently with pg_dump
Mailing lists >> pgsql-patches >> Thread
2008-06-09 22:43:43 | Tentative patch for making DROP put dependency info in DETAIL (Tom Lane)
time implementation of DROP TABLE is clearly exposed by the fact that you get multiple NOTICEs. I wonder if it would be worth refactoring the code so that a multiple-object DROP is implemented
Mailing lists >> pgsql-patches >> Thread >> Search in thread (2)
2008-05-19 06:03:25 | Re: [HACKERS] WITH RECURSIVE patch V0.1 (Martijn van Oosterhout)
server won't, the universe will end first. This is a nice example of the halting problem: http:///wiki/Halting_problem Which was proved unsolvable a long time
Mailing lists >> pgsql-patches >> Thread >> Search in thread (2)
2008-05-17 09:28:39 | Re: libpq object hooks (libpq events) (Andrew Chernow)
server_encoding_id 139 PQconnectionNeedsPassword 140 lo_import_with_oid 141 + PQcopyResult 142 + PQsetvalue 143 + PQresultAlloc 144 + PQregisterEventProc 145 + PQeventData 146 + PQresultEventData 147 Index: fe-connect.c =================================================================== RCS file: /projects/cvsroot/pgsql/src/interfaces/libpq/fe-connect.c,v retrieving revision 1.358 diff
Mailing lists >> pgsql-patches >> Thread
2008-05-16 05:01:12 | Re: Patch to change psql default banner v6 (David Fetter)
server-client mismatch only appear at startup time. This is a pretty clear POLA violation
Mailing lists >> pgsql-patches >> Thread
2008-05-05 14:50:57 | Re: configure option for XLOG_BLCKSZ (Simon Riggs)
time (like it usually does)? How would you manage a server farm like that? There
Mailing lists >> pgsql-patches >> Thread
2008-05-02 19:18:41 | Re: [COMMITTERS] pgsql: Sigh ... (Andrew Dunstan)
server listens and to which clients will try to connect. This can be overridden at run-time
Mailing lists >> pgsql-patches >> Thread
2008-04-30 07:11:27 | Re: pg_postmaster_reload_time() patch (Heikki Linnakangas)
server startup time if the configuration has never been reloaded. That's when the configuration
Mailing lists >> pgsql-patches >> Thread
2008-04-23 11:13:36 | Re: Improve shutdown during online backup, take 4 (Albe Laurenz)
time the server process is already forked. I couldn't see a way to check
Mailing lists >> pgsql-patches >> Thread >> Search in thread (2)
2008-04-15 14:45:04 | libpq object hooks patch (Andrew Chernow)
time) PQobjectHooks but leaving it out felt unbalanced. Note: PQhookData and PQresultHookData can be removed. There functionality can be reproduced by an API user issuing PQobjectHooks or PQresultObjectHooks and manually looking for there hook (normaly