Re: [HACKERS] Statement-level rollback

From: Thomas Munro With your v2 patch "make docs" fails. Here is a small patch to apply on top of yours to fix that and some small copy/paste errors, if I understood correctly. Ouch, thanks. I'd like to merge your fix when I submit the next revision of my patch. Regards MauMau --

Re: [HACKERS] Statement-level rollback

From: Simon Riggs On 14 August 2017 at 23:58, Peter Eisentraut wrote: > On 2/28/17 02:39, Tsunakawa, Takayuki wrote: >> The code for stored functions is not written yet, but I'd like your feedback for the specification and design based on the current patch. I'll

Re: [HACKERS] sync process names between ps and pg_stat_activity

ot fork WAL writer process: %m"))); Personally, I prefer "wal writer", "wal sender" and "wal receiver" that separate words as other process names. But I don't mind leaving them as they are now. I'd like to make this as ready for committer when I get some

Re: [HACKERS] [RFC] What would be difficult to make data models pluggable for making PostgreSQL a multi-model database?

Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [RFC] What would be difficult to make data models pluggable for making PostgreSQL a multi-model database?

gion's routines can be called. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] [RFC] What would be difficult to make data models pluggable for making PostgreSQL a multi-model database?

might be too dependent on the data model being relational, and it would be difficult to separate tight coupling. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] How can I find a specific collation in pg_collation when using ICU?

. -- Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [Q] When should I use reg* types instead of oid in the system catalog?

understood that it would do more harm than good to change existing plain oid columns to reg* types for various clients, and it wouldn't very beneficial but also not so harmful to make new catalogs/columns reg* types. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers

[HACKERS] [Q] When should I use reg* types instead of oid in the system catalog?

pg_trigger.tgfoid also have been changed to regproc? Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [patch] Build pgoutput with MSVC

/. I'm relieved to hear that's already committed. Oh, how careless I was, thanks. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [patch] Build pgoutput with MSVC

Also, I added an item in the Open Items page. Regards MauMau msvc_build_pgoutput_v2.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] [patch] Build pgoutput with MSVC

"mysub": ERROR: could not access file "pgoutput": No such file or directory postgres=# The pgoutput is not built with MSVC. The attached patch fixes this. I confirmed that a few INSERTs were replicated correctly. Should I add this matter in the PostgreSQL 10 Open Items p

Re: [HACKERS] BUG #13755: pgwin32_is_service not checking if SECURITY_SERVICE_SID is disabled

From: Heikki Linnakangas So, I think we still need the check for Local System. Thanks, fixed and confirmed that the error message is output in the event log. Regards MauMau win32-security-service-v7.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] Re: BUG #13755: pgwin32_is_service not checking if SECURITY_SERVICE_SID is disabled

Hi, Michael As I guessed in the previous mail, both our patches cause pgwin32_is_service() to return 1 even when SECURITY_SERVICE_RID is disabled, if the service is running as a Local System. The existing logic of checking for Local System should be removed. The attached patch fixes this

Re: [HACKERS] Re: BUG #13755: pgwin32_is_service not checking if SECURITY_SERVICE_SID is disabled

From: Michael Paquier Hm.. I have just tested HEAD, my patch and your patch using my patch test on pg_ctl.c, but I am always getting pgwin32_is_service set to 0 when running pg_ctl start from a terminal, and set it to 1 when running pg_ctl service to register the service startup. Could you precise

Re: [HACKERS] BUG #13755: pgwin32_is_service not checking if SECURITY_SERVICE_SID is disabled

Hello, Sorry, I may have had to send this to pgsql-hackers. I just replied to all, which did not include pgsql-hackers but pgsql-bugs because this discussion was on pgsql-bugs. CommitFest app doesn't seem to reflect the mails on pgsql-bugs, so I'm re-submitting this here on pgsql-hackers.

Re: [HACKERS] [bug fix] pg_recvlogical is missing in the Windows installation

From: Robert Haas On Sat, Sep 17, 2016 at 7:44 PM, Michael Paquier <michael.paqu...@gmail.com> wrote: > On Sun, Sep 18, 2016 at 7:01 AM, MauMau <maumau...@gmail.com> wrote: >> pg_recvlogical is not included in the Windows client installation, >> which is performed

[HACKERS] [bug fix] pg_recvlogical is missing in the Windows installation

Hello, pg_recvlogical is not included in the Windows client installation, which is performed by running "install client". The attached patch based on HEAD fixes this. I confirmed nothing else is missing in the client installation. Regards MauMau (= Takayuki

Re: [HACKERS] How can we expand PostgreSQL ecosystem?

to the catalog. Regards MauMau

Re: [HACKERS] How can we expand PostgreSQL ecosystem?

for commercial databases? Change the name :p -- Sorry, I couldn't catch the implication. Do you mean changing the name PostgreSQL to something else, or just a joke? Regards MauMau

[HACKERS] How can we expand PostgreSQL ecosystem?

grating from commercial databases? What is the effective way to absorb user requests for this? Is it enough to make a questionnaire like the following? What is the popular questionnaire site which can catch many users (SurveyMonkey?) https://postgresql.uservoice.com/forums/21853-general Regards MauMau

Re: [HACKERS] Greeting for coming back, and where is PostgreSQL going

. There are discussions about backporting stuff from XC/XL back to core, though that's a tough work. This thread is a good summary of what is happening lately in this area: http://www.postgresql.org/message-id/20160223164335.ga11...@momjian.us Cool, exciting to know this! Regards MauMau -- Sent via

[HACKERS] Greeting for coming back, and where is PostgreSQL going

for helping me. After that, I had to stay away from the community for some reason. Now, I'd be happy if I can contribute to PostgreSQL again. But please excuse me for my slow restart, as the blank period needs some rehabilitation. Let me briefly introduce myself. I'm MauMau, this is a nickname

Re: [HACKERS] pgaudit - an auditing extension for PostgreSQL

commas? Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] pgaudit - an auditing extension for PostgreSQL

looks good. However, I'm worried about the maintenance. How can developers notice that pgaudit.c needs modification when they add a new SQL statement? What keyword can they use to grep the source code to find pgaudit.c? Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] [9.4 bug] The database server hangs with write-heavy workload on Windows

From: MauMau maumau...@gmail.com Thank you very much. I didn't anticipate such a difficult complicated cause. The user agreed to try the patch tonight. I'll report back the result as soon as I got it from him. The test ran successfully without hang for 24 hours. It was run with your

Re: [HACKERS] [9.4 bug] The database server hangs with write-heavy workload on Windows

= lock-head; Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [9.4 bug] The database server hangs with write-heavy workload on Windows

) InterlockedExchange(lock, 0) FYI, the user reported today that the problem didn't occur when he ran the same test for 24 hours on 9.3.5. Do you see something relevant in 9.4? Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] pgaudit - an auditing extension for PostgreSQL

MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] [9.4 bug] The database server hangs with write-heavy workload on Windows

Hello, One user reported a hang problem with 9.4 beta2 on Windows. The PostgreSQL is 64-bit version. I couldn't find the cause, but want to solve the problem. Could you help with this? I heard that the user had run 16 concurrent psql sessions which executes INSERT and UPDATE statements,

Re: [HACKERS] [9.4 bug] The database server hangs with write-heavy workload on Windows

anyway. How were the stacks captured - what tool? According to his mail, Windbg or userdump.exe. I'll ask him about this. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [9.4 bug] The database server hangs with write-heavy workload on Windows

records. I'll ask him again. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [patch] pg_copy - a command for reliable WAL archiving

like to avoid duplicate work basically. If there exists such a command available in the standard OS installation, I want to use it. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref

Re: [HACKERS] proposal for 9.5: monitoring lock time for slow queries

the data erasure during recovery. We can probably extend pg_statsinfo to save the new info for long-term trend analysis. TBH, I want a feature like pg_statsinfo in core. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] Enable WAL archiving even in standby

a new section for disaster recovery that describes concrete parameter settings (e.g. how do we discard old archive WAL files after taking a base backup from standby, because backup label file is not created?). Good luck! Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] option -T in pg_basebackup doesn't work on windows

Thank you. The code looks correct. I confirmed that the pg_basebackup could relocate the tablespace directory on Windows. I marked this patch as ready for committer. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription

Re: [HACKERS] Improvement of versioning on Windows, take two

I confirmed that all issues are solved. The patch content looks good, alghouth I'm not confident in Perl. I marked this patch as ready for committer. I didn't try the patch on MinGW. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes

Re: [HACKERS] proposal for 9.5: monitoring lock time for slow queries

in the manual how to diagnose and tne the system with these event info. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] proposal for 9.5: monitoring lock time for slow queries

using SQL queries. This prevents the development of performance diagnostics functionality in GUI administration tools. Also, statistics views allow for easy access on PAAS like Amazon RDS and Heroku. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [HACKERS] proposal for 9.5: monitoring lock time for slow queries

From: Pavel Stehule pavel.steh...@gmail.com 2014-08-13 13:59 GMT+02:00 MauMau maumau...@gmail.com: Are you concerned about the impactof collection overhead on the queries diagnosed? Maybe not light, but I'm optimistic. Oracle has the track record of long use, and MySQL provides performance

Re: [HACKERS] option -T in pg_basebackup doesn't work on windows

integer. char*linkloc = psprintf(%s/pg_tblspc/%d, basedir, oid); Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [patch] pg_copy - a command for reliable WAL archiving

I fixed some minor mistakes. Regards MauMau pg_copy_v3.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [RFC] Should smgrtruncate() avoid sending sinval message for temp relations

functions which have the same contents. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Improvement of versioning on Windows, take two

properties. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Improvement of versioning on Windows, take two

/cab7npqrty1eikqgmz1_wbvhpvfyve9vma67ricepq6d8-eg...@mail.gmail.com LINK : fatal error LNK1104: ファイル '.\release\postgres\src_timezone_win32ver.obj' を開くことができません。 Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [HACKERS] [RFC] Should smgrtruncate() avoid sending sinval message for temp relations

session 1, run any SQL statement. It doesn't reply. The backend is stuck at SyncRepWaitForLSN(). Regards MauMau sinval_catchup_hang_v3.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] [RFC] Should smgrtruncate() avoid sending sinval message for temp relations

From: MauMau maumau...@gmail.com I must add one thing. After some client processes closed the connection without any hang, their server processes were stuck with a stack trace like this (I'll look for and show the exact stack trace tomorrow): I found two kinds of stack traces: #0

Re: [HACKERS] [RFC] Should smgrtruncate() avoid sending sinval message for temp relations

with the latch and SIGUSR1 mechanism. How can we fix this problem? Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [RFC] Should smgrtruncate() avoid sending sinval message for temp relations

()) due to the SIGUSR1 issued for sinval catchup event? How should we tackle these problem? Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [RFC] Should smgrtruncate() avoid sending sinval message for temp relations

you hink of for back-patching? Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] [RFC] Should smgrtruncate() avoid sending sinval message for temp relations

. Is this correct? if (SmgrIsTemp(reln)) /* Do his on behalf of sinval message handler */ smgrclosenode(reln-smgr_rnode); else CacheInvalidateSmgr(reln-smgr_rnode); Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] [RFC] Should smgrtruncate() avoid sending sinval message for temp relations

necessary for session-private objects like temp relations. I thought shared inval is, as the name indicates, for objects shared among sessions. If so, sinval for session-private objects doesn't seem to match the concept. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] [bug fix] Suppress autovacuum: found orphan temp table message

From: Andres Freund and...@2ndquadrant.com On 2014-07-22 10:09:04 +0900, MauMau wrote: Is there any problem if we don't output the message? Yes. The user won't know that possibly gigabytes worth of diskspace aren't freed. RemovePgTempFiles() frees the disk space by removing temp relation

Re: [HACKERS] [bug fix] Suppress autovacuum: found orphan temp table message

From: Andres Freund and...@2ndquadrant.com On 2014-07-22 17:05:22 +0900, MauMau wrote: RemovePgTempFiles() frees the disk space by removing temp relation files at server start. But it's not called during a crash restart. Yes, the comment of the function says: * NOTE: we could, but don't

Re: [HACKERS] [bug fix] Suppress autovacuum: found orphan temp table message

From: Andres Freund and...@2ndquadrant.com On 2014-07-22 19:13:56 +0900, MauMau wrote: But this is true if restart_after_crash = on in postgresql.conf, because the crash restart only occurs in that case. However, in HA cluster, whether it is shared-disk or replication, restart_after_crash

Re: [HACKERS] [bug fix] Suppress autovacuum: found orphan temp table message

the patch tomorrow? (I'm not confident I can finish it...) I'd really appreciate it if you could create the fix, if tomorrow will be late. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [HACKERS] [bug fix] Suppress autovacuum: found orphan temp table message

From: Andres Freund and...@2ndquadrant.com On 2014-07-18 23:38:09 +0900, MauMau wrote: So, I propose a simple fix to change the LOG level to DEBUG1. I don't know which of DEBUG1-DEBUG5 is appropriate, and any level is OK. Could you include this in 9.2.9? Surely that's the wrong end

Re: [HACKERS] [bug fix] Suppress autovacuum: found orphan temp table message

From: Andres Freund and...@2ndquadrant.com On 2014-07-18 23:38:09 +0900, MauMau wrote: LOG: autovacuum: found orphan temp table pg_temp_838.some_table in database some_db LOG: autovacuum: found orphan temp table pg_temp_902.some_table in database some_db So they had server crashes of some

Re: [HACKERS] [bug fix] pg_ctl always uses the same event source

, and thank you very much for kind and repeated review and help, Amit-san. Regards MauMau pgevent.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [bug fix] pg_ctl always uses the same event source

, or -e should be placed in the section Options instead of Options for Windows? Regards MauMau pg_ctl_eventsrc_v11.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref

Re: [HACKERS] [bug fix] pg_ctl always uses the same event source

above. I noticed the continued discussion after I had prepared and submitted the revised patch. OK, how about the patch in the previous mail, Magnus-san? Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] [bug fix] pg_ctl always uses the same event source

. Regards MauMau pg_ctl_eventsrc_v10.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [bug fix] pg_ctl always uses the same event source

MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Proposing pg_hibernate

think that Buffer Saver should first write to a temp file, say *.tmp, then rename it to *.save upon completion. That prevents the Block Reader from reading possibly corrupted half-baked file that does not represent any hibernated state. Regards MauMau -- Sent via pgsql-hackers mailing list

Re: [HACKERS] [bug fix or improvement?] Correctly place DLLs for ECPG apps in bin folder

/ } } But the source tree contains as many as 206 Makefiles. I'm worried that it will waste the install time. Should all these Makefiles be examined, or 16 Makefiles in src/interfaces/? Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] [RFC: bug fix?] Connection attempt block forever when the synchronous standby is not running

From: Amit Kapila amit.kapil...@gmail.com On Fri, Jul 4, 2014 at 7:29 PM, MauMau maumau...@gmail.com wrote: [Hypothesis] Why does the connection processing emit WAL? Probably, it did page-at-a-time vacuum during access to pg_database and pg_authid for client authentication. src/backend

Re: [HACKERS] [RFC: bug fix?] Connection attempt block forever when the synchronous standby is not running

slightly less data protection than maximum availability mode and has minimal impact on primary database performance. == Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] [RFC: bug fix?] Connection attempt block forever when the synchronous standby is not running

even if * we are waiting for standbys to connect. This is important to ensure we * aren't blocked from performing anti-wraparound tasks. */ if (synchronous_commit SYNCHRONOUS_COMMIT_LOCAL_FLUSH) SetConfigOption(synchronous_commit, local, PGC_SUSET, PGC_S_OVERRIDE); Regards MauMau

Re: [HACKERS] [RFC: bug fix?] Connection attempt block forever when the synchronous standby is not running

transaction case? I'd appreciate any opinion on this, too. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [bug fix or improvement?] Correctly place DLLs for ECPG apps in bin folder

MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Proposing pg_hibernate

markSavefileBeingRestored Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] [RFC: bug fix?] Connection attempt block forever when the synchronous standby is not running

. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] pgaudit - an auditing extension for PostgreSQL

functionality. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [Fwd: Re: [HACKERS] proposal: new long psql parameter --on-error-stop]

Thanks, I marked it as ready for committer. I hope Fujii san or another committer will commit this, refining English expression if necessary. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [Fwd: Re: [HACKERS] proposal: new long psql parameter --on-error-stop]

if you retain or remove the description. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [Fwd: Re: [HACKERS] proposal: new long psql parameter --on-error-stop]

subsequently printed tables\n)); This is all I noticed in the review. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [Fwd: Re: [HACKERS] proposal: new long psql parameter --on-error-stop]

. And this section lacks description for Windows, such as: + printf(_( NAME=VALUE [NAME=VALUE] psql ...\n or \\setenv NAME [VALUE] in interactive mode\n\n)); + printf(_( PGPASSFILE password file (default ~/.pgpass)\n)); Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql

Re: [HACKERS] PostgreSQL in Windows console and Ctrl-C

as well like start and restart mode for clarification. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Use a signal to trigger a memory context dump?

for performance. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] proposal: new long psql parameter --on-error-stop

data as INSERT commands with column names ok I fixed it Thank you. I marked this patch as ready for committer. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] PostgreSQL in Windows console and Ctrl-C

by + commandpg_ctl/command when called with the + optionstart/option subcommand. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] proposal: new long psql parameter --on-error-stop

/pg_dumpall.c for similar switches. - while ((c = getopt_long(argc, argv, aAc:d:eEf:F:h:HlL:no:p:P:qR:sStT:U:v:VwWxXz?01, or+ while ((c = getopt_long(argc, argv, aAc:d:eEf:F:h:HlL:no:p:P:qR:sStT:U:v:VwWxXz?001, Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [HACKERS] proposal: new long psql parameter --on-error-stop

with each other, whether they are short or long. -x, --no-privileges do not dump privileges (grant/revoke) --binary-upgrade for use by upgrade utilities only --column-inserts dump data as INSERT commands with column names Regards MauMau -- Sent via pgsql

Re: [HACKERS] [bug fix] Memory leak in dblink

issues if other modules had similar bugs, in addition to the original dblink problem, wouldn't this? Definitely +1. The original OP wants to use 9.2. I'll report to him when you've committed this nce patch. Thanks, Tom san. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql

Re: [HACKERS] Removing dependency to wsock32.lib when compiling code on WIndows

libraries from their names. Could you look into this and revise the patch if possible? But I don't mind if you do so. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [bug fix] Memory leak in dblink

and deletion is a waste of processing. I think the original author wanted to eliminate this waste by creating the context when dblink() should return a row. I'd like to respect his thought. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] [bug fix] Memory leak in dblink

this, because sinfo is zero-cleared. PG_TRY(); { + /* Create short-lived memory context for data conversions */ + sinfo.tmpcontext = AllocSetContextCreate(CurrentMemoryContext, +dblink temporary context, Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] datistemplate of pg_database does not behave as per description in documentation

-templatedbs.html Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Removing dependency to wsock32.lib when compiling code on WIndows

these files as well for code cleanup? ./configure ./configure.in ./contrib/pgcrypto/Makefile ./src/interfaces/libpq/Makefile ./src/interfaces/libpq/win32.c ./src/interfaces/libpq/win32.mak ./src/test/thread/README ./src/tools/msvc/Mkvcbuild.pm Regards MauMau -- Sent via pgsql-hackers mailing

Re: [HACKERS] datistemplate of pg_database does not behave as per description in documentation

From: Fujii Masao masao.fu...@gmail.com On Wed, Jun 18, 2014 at 7:47 PM, MauMau maumau...@gmail.com wrote: I marked this as ready for committer. The patch is good because it matches the description in the following page: http://www.postgresql.org/docs/devel/static/manage-ag-templatedbs.html

[HACKERS] [patch] pg_copy - a command for reliable WAL archiving

Hello, As I proposed before in the thread below, I've implemented a simple command for reliable WAL archiving. I would appreciate it if you could review and test the patch. http://www.postgresql.org/message-id/9C1EB95CA1F34DAB93DF549A51E3E874@maumau Regards MauMau pg_copy.patch

Re: [HACKERS] [patch] pg_copy - a command for reliable WAL archiving

From: Joe Conway m...@joeconway.com That first hunk refers to dblink -- I'm guessing it does not belong with this patch. Ouch, what a careless mistake. The attached one is clean. I'll update the CommitFest entry when I'm back home from work. Regards MauMau pg_copy_v2.patch Description

Re: [HACKERS] [bug fix] Memory leak in dblink

places where PG_CATCH() is used, memory context is not deleted. So, I removed the modification from PG_CATCH() block. Thanks. Regards MauMau dblink_memleak_v2.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

[HACKERS] [bug fix] Memory leak in dblink

Horiguchi, Marko Kreen) Regards MauMau dblink_memleak.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [bug fix] Memory leak in dblink

is only posted to pgsql-hackers and/or pgsql-bugs, it might be forgotten. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Supporting Windows SChannel as OpenSSL replacement

stored in its HSM product. Intel offered AES-NI implementation code to OpenSSL community. I guess OpenSSL will continue to be the most functional and obtain the widest adoption and support. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes

Re: [HACKERS] [bug fix] pg_ctl always uses the same event source

From: Amit Kapila amit.kapil...@gmail.com I think it's bit late for this patch for 9.4, you might want to move it to next CF. Thanks, I've moved it. It's a regret that this very small patch wasn't put in 9.4. Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] [bug fix] pg_ctl always uses the same event source

variable on all platforms like register_servicename, although they are not necessary on non-Windows platforms. Regards MauMau pg_ctl_eventsrc_v9.patch Description: Binary data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] 9.4 release notes

/patch_view?id=1326 Regards MauMau -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] elog a stack trace

if PostgreSQL outputs the stack trace of a crashing postgres process in the server log. That eliminates the need for users in many cases to send the huge core files to the support staff or to use the debugger to get the stack trace. I've recently heard that MySQL has this feature. Regards MauMau

  1   2   3   4   >