d 9.6? Are you
recommending other developers not implement these features to avoid
duplication of work with AXLE?
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
mpatibility (this should be very important
to get many users in practice), etc. I think eye-catching features like
streaming replication and materialized views are necessary to widen
PostgreSQL use.
* Explain new features by associating them with the new trends like cloud,
mobile, social, bi
size);
Oh, removed.
Sorry for delayed response and I am not sure that I will be able to
complete the review of patch in next few days as I will be on vacation.
OK, I'm waiting for you. Please have a nice vacation.
Regards
MauMau
pg_ctl_eventsrc_v8.patch
Description: Binary data
-
ot; sets the
event source name for pg_ctl to use. When -e is used with pg_ctl register,
it will be added to the command line for Windows service (pg_ctl
runservice).
Regards
MauMau
pg_ctl_eventsrc_v7.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@post
InRecovery)
{
struct stat st;
Defining stat struct two times in same function in different ways doesn't
seem to be good, we can do the same way for new usage as is already
done in code or may be declare it once.
OK, I removed the second (existing) definition of st.
Regards
MauMau
remov
here is no such scenario, I think your code is
right as stat/isdir check seems to be okay to identify junction
points and it avoids ifdef WIN32 check (which I personally think
is bit annoying and we should try to avoid such code unless it
is must or provides any significant advantage).
I think so, too.
other undesirable point in the current doc. To overcome this,
someone on this ML recommended me to do "cp %p /archive/dir/%f.tmp && mv
/archive/dir/%f.tmp /archive/dir/%f". Does this solve your problem?
Regards
MauMau
--
Sent via pgsql-hackers mailing list (pgsql
From: "Alvaro Herrera"
MauMau escribió:
The "raw" link only gave the mail in text format. I hoped to import
the mail into Windows Mail on Windows Vista, but I couldn't.
You might need to run a conversion process by which you transform the
raw file (in mbox f
From: "Michael Paquier"
On Fri, Mar 21, 2014 at 8:54 PM, MauMau wrote:
* Create pg_copy in C so that it can be used on Windows as well as on
UNIX/Linux. It just copies one file. Its source code is located in
src/bin/pg_copy/. Please recommend a better name if you have one in
From: "Michael Paquier"
On Fri, Mar 21, 2014 at 8:54 PM, MauMau wrote:
* Create pg_copy in C so that it can be used on Windows as well as on
UNIX/Linux. It just copies one file. Its source code is located in
src/bin/pg_copy/. Please recommend a better name if you have one in
op standby
6) change max_connections on the standby
7) start standby
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
record at
startup when the parameter value in postgresql.conf does not match the one
in pg_control. Then, the WAL record is sent to the standby and applied,
which changes the value in pg_control on the standby.
Regards
MauMau
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgres
From: "Mitsumasa KONDO"
2014-03-17 21:12 GMT+09:00 Fujii Masao :
On Mon, Mar 17, 2014 at 10:20 AM, Robert Haas
wrote:
> On Sun, Mar 16, 2014 at 6:23 AM, MauMau wrote:
>> * Improve the example in the documentation.
>> But what command can we use to re
sion.
OK, done. Please find the attached patch. I also rebased the patch to
HEAD.
I'll update the CommitFest entry soon.
Regards
MauMau
remove_tblspc_symlink_v5.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to yo
From: "Amit Kapila"
On Wed, Jan 15, 2014 at 8:12 PM, MauMau wrote:
Thanks for reviewing and testing the patch. Yes, at first I did what you
mentioned, but modified the patch according to some advice in the mail
thread. During redo, create_tablespace_directories() needs to handl
ot correct, because it only checks the existence of the
file. What if the file size is less than 16MB? How can we check if the
file is completely archived?
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
ted to this topic, pg_basebackup doesn't fsync the backed up files. I'm
afraid this too is different from what the users expect --- I guess they
would expect the backup is certainly available after pg_basebackup completes
even if the machine crashes.
Regards
MauMau
--
Sent via pgsql-
be wrapped
Monday (3/17) for public announcement Thursday (3/20).
Regarding:
Prevent intermittent "could not reserve shared memory region" failures on
recent Windows versions (MauMau)
Could you include the patch I sent for 9.0/9.1 in response to Magnus san?
http://www.postg
o. I'll communicate this to the
PL/Java community.
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
From: "Alvaro Herrera"
MauMau escribió:
Do you know how I can reply to an email which was deleted locally?
I thought I could download an old mail by clicking "raw" link and
import it to the mailer. However, it requires username/password
input, and it seems to be differ
From: "Tom Lane"
"MauMau" writes:
To put the question in other words, is it safe to load a multi-threaded
PL
library in the single-threaded backend process, if the PL only calls SPI
in
the main thread?
When it breaks, we're not going to be concerned.
I may n
arked needs for review by
misunderstanding Tom-san's opinion.
I remember that I read "silence means no objection, or implicit agreement"
somewhere in the community site or ML. So I think it would be no problem to
set the status to ready for committer again.
Regards
MauMau
--
Se
RCE should be used. For more information please refer to
the native compiler documentation.
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
From: "Rajeev rastogi"
Please find the attached modified patch.
Thanks, reviewed and made this patch 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/mail
owing
lines. If the "Dynamic base" line is displayed, ASLR is enabled. If this
line disappears, ASLR is disabled.
8140 DLL characteristics
Dynamic base
NX compatible
Terminal Server Aware
Regards
MauMau
disable_ASLR_pg9
.
(1)
Add the function name in the comment as in:
/*
* make_absolute_path
*
* ...existing function descripton
*/
(2)
Add errno description as in:
fprintf(stderr, _("could not get current working directory: %s\n",
strerror(errno)));
Regards
MauMau
--
Sent via pgsql-hackers ma
Yes, I limited the change only to Windows, because I thought I might get get
objection against unnecessary change. Plus, --single should not be allowed
for root, because root cannot be the PostgreSQL user account.
Regards
MauMau
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresq
still wonder a bit why the latency spike became so
bigger even with # of clients fewer than # of CPU cores. I suppose the
requests get processed more smoothly when the number of simultaneous
requests is small. Anyway, I want to believe the latency spike would become
significantly smaller on a
lly supported on those Windows versions
unless you apply the registry workaround?
I'll try it at least for 9.1 in a few days when time permits. The fix
should be adding only one line in Project.pm.
Regards
MauMau
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
e the declaration in miscadmin.h.
4. Modify make_absolute_path() in path.c so that it can be used both in
backend and frontend. That is, surround the error message output with
#ifdef FRONTEND ... #else ... #endif. See some other source files in
src/port.
Regards
MauMau
--
Sent via pgsql-hackers
From: "Andres Freund"
On 2014-02-18 01:35:52 +0900, MauMau wrote:
For example, please see the max latencies of test set 2 (PG 9.3) and test
set 4 (xlog scaling with padding). They are 207.359 and 1219.422
respectively. The throughput is of course greatly improved, but I think
th
bt_insert(), but I'm not sure.
When the hang occurred, INSERT/UPDATE/COMMIT statements stopped for at least
one hour, while SELECT statements ran smoothly.
Regards
MauMau
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www
From: "Andres Freund"
On 2014-02-18 00:43:54 +0900, MauMau wrote:
I'm worried about the big increase in max latency. Do you know the
cause?
More frequent checkpoints caused by increased WAL volume thanks to
enhanced
performance?
I don't see much evidence of increase
tributed quite evenly across the slots.
*/
if (slotno != -1 && retry)
slotToTry = (slotToTry + 1) % num_xloginsert_slots;
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
c, but if you'd test that those handle your problem cases,
I'd appreciate it.
I confirmed that the problem disappeared. I'll delete my CommitFest entry
in several days.
Regards
MauMau
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
eFrom: "Andres Freund"
could you try if you get more readable dumps by using disassemble/m?
That might at least print line numbers if you have debug info installed.
Please find the attached file. I hope this will reveal something.
Regards
MauMau
Dump of assembler code fo
From: "Bruce Momjian"
On Mon, Dec 2, 2013 at 10:22:47PM +0900, MauMau wrote:
So, my suggestion is to just add the following sentence right after
the above one.
The Postgres style is an exception: the output of the date type is
either MM-DD- (e.g. 12-17-1997) or DD-MM- (
Could you include this simple patch in the upcoming minor release
9.3.3/9.2.7/9.1.12? This is very scary. This problem would cause much
random trouble among Windows users.
https://commitfest.postgresql.org/action/patch_view?id=1409
Regards
MauMau
--
Sent via pgsql-hackers mailing list
selves, not the community RPM nor
EnterpriseDB's installer.
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
ttached patch keeps restored archived WAL in pg_xlog/ only during standby
recovery. It is based on Fujii-san's revison of the patch, with
AllowCascadeReplication() condition removed from two if statements.
Regards
MauMau
wal_increase_in_pitr_v4.patch
Description: Binary data
--
Sent
ionCommand ()
#6 0x00664cf7 in finish_xact_command ()
#7 0x00667145 in exec_simple_query ()
#8 0x00668058 in PostgresMain ()
#9 0x00622ef1 in PostmasterMain ()
#10 0x005c0723 in main ()
Regards
MauMau
Dump of assembler code for function LWLockRelease:
0x00
s for this. So I felt there is something wrong with lwlocks.
Do you think that your question could cause my customer's problem --
backends block at lwlock forever?
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
27;s a workaround in the
mean time.
Please don't mind, I didn't misunderstand your intent. I think we should
apply this in the next minor release to avoid unnecessary confusion -- more
new users would use PostgreSQL on Windows 8/2012 and hit this problem.
I added this patch to t
You are right. Fixed.
Regards
MauMau
remove_tblspc_symlink_v4.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
From: "Rajeev rastogi"
I will update commitFest with the latest patch immediately after sending
the mail.
OK, done setting the status to ready for committer.
Regards
MauMau
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscrip
Finally, please change the function description comment of
get_absolute_path() so that the style follows other function in path.c.
That is:
/*
*
*
* Function description
*/
Then update the CommitFest entry with the latest patch and let me know of
that. Then, I'll change the patch sta
hat are not affected by
ASLR.
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
of find_my_abs_path() to "path", because
file is also a path.
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
using the debugger.
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
e explaining
about setting of event log i.e at below link or may be if you find some
other
better place:
http://www.postgresql.org/docs/devel/static/runtime-config-logging.html#GUC-LOG-DESTINATION
Please let us make this a separate patch. I agree with you about the place
in the manual.
Re
From: "Christian Kruse"
personally I really dislike constructs like you used:
Thanks for reviewing the patch. Fixed. I'll add this revised patch to the
CommitFest entry soon.
Regards
MauMau
config_dir_win_v2.patch
Description: Binary data
--
Sent via pgsql-hackers mail
ndle the testing
of pg_ctl.
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
I'm sorry for the late reply. I was unable to access email.
From: "Craig Ringer"
On 01/24/2014 06:42 PM, MauMau wrote:
The customer is using 64-bit PostgreSQL 9.1.x
Which "x"?
9.1.6.
Does this issue also occur on 9.3.2, or in 9.4 HEAD, when tested on
Win2k12?
From: "Fujii Masao"
On Fri, Jan 24, 2014 at 9:00 PM, MauMau wrote:
OTOH, regarding PQhost(), I think we had better take my patch.
connectOptions2() computes and set derived values to PGconn, so that
PGconn's members have values which are actually used for connection. To
f
out of disk space in archive
recovery, I wonder if we should perform restartpoints more aggressively.
We
intentionally don't trigger restatpoings by checkpoint_segments, only
checkpoint_timeout, but I wonder if there should be an option for that.
That's an option.
MauMau, did you t
sockets. Plus, if we want to refer to the actual
connection target for libpq implementation in other places than PQhost(), we
can just use PGconn's members. If we do so, we don't have to change
PQhost().
Could you replace the patch?
Regards
MauMau
--
Sent via pgsql-hackers mai
Hi, Heiki-san,
From: "MauMau"
From: "Heikki Linnakangas"
After some refactoring and fixing bugs in the existing code, I came up
with the attached patch. I called the option simply "recovery_target",
with the only allowed value of "immediate". IOW,
From: "MauMau"
OK, I added several lines for this. Please check the attached patch.
I'm sorry, I attached the old patch as v5 in my previous mail. Attached on
this mail is the correct one.
I'll update the CommitFest entry soon.
Regards
MauMau
pg_ctl_eventsrc_
g
output in my customer's environment.
I'll add this to the CommitFest if necessary.
Regards
MauMau
disable_ASLR.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
added some documentation, as
well as modifying the usage at the end of install.pl.
I'll update the CommitFest entry shortly.
Regards
MauMau
client_only_install_win_v2.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to yo
t, because syslog_ident also has the default value "postgres",
which doesn't contain the major release.
Any (not complicated) suggestions?
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
pg_ctl use the event_source setting. Anyway, not all
parameters in postgresql.conf cannot be used just by uncommenting them.
That's another issue.
I'll update the CommitFest entry soon.
Regards
MauMau
pg_ctl_eventsrc_v5.patch
Description: Binary data
--
Sent via pgsql-hackers m
ata in another directory
#max_stack_depth = 2MB # min 100kB
#include_if_exists = 'exists.conf' # include file only if it exists
#include = 'special.conf' # include file
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
y registered."
Please correct me if there's better expression in English.
Are there any other suggestions to make this patch ready for committer? I'd
like to make all changes in one submission.
Regards
MauMau
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.or
something similar to
what you were reporting "event source not found".
Am I missing something?
Steps
1. installation of PostgreSQL from source code using Install.bat in
mdvc directory
2. initdb -D
3. regsvr32 /n /i:PostgreSQL \lib\pgevent32.dll
Please specify pgevent.dll, not pgevent
ry even
on UNIX/Linux. Please see TablespaceCreateDbspace is().
destroy_tablespace_directories() doesn't have to handle such situation.
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
ntered an all-zero
page. How did the all-zero page appear on the standby? Was it transferred
from master by pg_basebackup? FYI, the server log didn't contain any
messages related to disk full, nor any ERROR messages.
Regards
MauMau
--
Sent via pgsql-hackers mailing list (pgsql-hack
From: "Michael Paquier"
On Fri, Jan 10, 2014 at 12:08 AM, MauMau wrote:
C2. "recovery_target = 'immediate'" sounds less intuitive than my
suggestion
"recovery_target_time = 'backup_point'", at least for those who want to
recover to the backu
From: "Hannu Krosing"
On 01/09/2014 01:57 PM, MauMau wrote:
Let me ask a (probably) stupid question. How is the sync rep
different from RAID-1?
When I first saw sync rep, I expected that it would provide the same
guarantees as RAID-1 in terms of durability (data is always mirro
t in what use cases do they specify this parameter? For example,
when do the users face the following situation?
I was thinking that you have a warm standby server, and you decide to
stop using it as a warm standby, and promote it. You'd do that by
stopping it, modifying recovery.conf to remove standby_mode, and set a
recovery target, and then restart.
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
From: "Robert Haas"
Suppose the startup packet itself is malformed. How will you report the
error?
I think we have no choice but to report the error in English, because we
don't know what the client wants.
Regards
MauMau
--
Sent via pgsql-hackers mailing list
From: "Robert Haas"
Suppose the startup packet itself is malformed. How will you report the
error?
I think we have no choice but to report the error in English, because we
don't know what the client wants.
Regards
MauMau
--
Sent via pgsql-hackers mailing list
nd availability (if one server goes down, another server continues
full service).
The cost is reasonable with RAID-1. The sync rep requires high cost to get
both durability and availability --- three servers.
Am I expecting too much?
Regards
MauMau
--
Sent via pgsql-hackers mail
From: "Bruce Momjian"
On Sun, Jan 5, 2014 at 04:40:17PM +0900, MauMau wrote:
Then, as a happy medium, how about disabling message localization
only if the client encoding differs from the server one? That is,
compare the client_encoding value in the startup packet with the
startup packet with the result of
GetPlatformEncoding(). If they don't match, call
disable_message_localization().
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
From: "Peter Eisentraut"
On 12/25/13, 6:40 AM, MauMau wrote:
pg_regress must wait for postgres to terminate by calling waitpid(),
because it invoked postgres directly. The attached
pg_regress_pg_stop.patch does this. If you like the combination of this
and the original fix for pg_
From: "Michael Meskes"
On Sat, Dec 28, 2013 at 08:04:09AM +0900, MauMau wrote:
OK, I'll run the ECPG regression test on Solaris without the patch.
Please wait until Jan 6 2014 or so, because we've just entered new
year holidays here in Japan.
Sure, we're no in a part
u for committing the fix. I'm comfortable with your change.
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
in the past several years, but those were not
solved. There seems to be a big dangerous bug hiding somewhere.
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
instead of the desired server-host, and fails to
connect because the database server is not running on client-host. This is
because ECPGconnect() passes an empty string (""), not NULL, to
PQconnectdbParams().
Regards
MauMau
--
Sent via pgsql-hackers mailing list (pgsql-hacker
From: "Michael Meskes"
On Tue, Dec 17, 2013 at 09:26:49PM +0900, MauMau wrote:
[Problem]
The ECPG app runs the statement:
EXEC SQL CONNECT TO 'tcp:postgresql://?service=my_service';
...
ECPGconnect() parses the URI and produces an empty host name. It
passes an empty str
evant to the
actual processing. I thought the original 0 was chosen arbitrarily and I
could do so too. If I can do better, please let me know that.
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
exit code was 256
pg_ctl timed out waiting for the zombie postgres.
maumau 19621 18849 0 15:21 pts/900:00:00 [postgres]
maumau 20253 18849 0 15:22 pts/900:00:00
/maumau/postgresql-9.4/src/test/regress/./tmp_check/install//maumau/pgsql/bin/pg_ctl
stop -D /maumau/postgresql-9.4/src/te
From: "Boszormenyi Zoltan"
The app wasn't attached, only the patch.
If this is a small test app, it can also be a part of the patch in the
form of a
regression test.
Sorry, attached. Thank you for pointing it out.
Regards
MauMau
sigbus.pgc
Description: Binary data
--
ligned on 8-byte boundary. This unaligned access causes SIGBUS.
[Fix]
Because desc1 is a char array, else block should be executed instead of the
above path.
var->value = var->pointer;
Therefore, make ecpg pass SQL descriptor host variables to ECPGdo() with
non-zero leng
sible to figure out. If the message is in english, at least it
can be searched for in the web, or something -- the user might even find
a page in which the english error string appears, with a native language
explanation.
I feel like this, too. Being readable in English is better than being
unr
essage transmission fails in PQputCopyEnd(), switch
conn->asyncStatus back to PGASYNC_BUSY. That causes PQgetResult() to try to
read data with pqReadData(). pqReadData() fails and PQgetResult() returns
NULL. As a consequence, the loop in question terminates.
Regards
MauMau
failed_copy_lo
veryPath, MAXPGPATH, XLOGDIR "/RECOVERYXLOG");
- unlink(recoveryPath); /* ignore any error */
-
Regards
MauMau
wal_increase_in_pitr_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
rg/docs/devel/static/event-log-registration.html
http://www.postgresql.org/docs/devel/static/runtime-config-logging.html#GUC-EVENT-SOURCE
Okay, done. Thanks. I'll update the commitfest entry this weekend.
Regards
MauMau
pg_ctl_eventsrc_v4.patch
Description: Binary data
--
Sent via p
not to be
evicted from the cache (like Oracle's KEEP buffer?), for the same reason as
1.
I'd love such useful feature like pg_rewarm to be included in core. I hope
such nice features won't be rejected just because there are already similar
external tools.
Regards
MauMau
r ECPGconnect() to pass an empty host name to
PQconnectdbParams(), so prevent it from passing host parameter for the
service setting to take effect. port is the same.
Regards
MauMau
ecpg_service.patch
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.or
nt in pg_ctl.c just below
RegisterEventSource call.
Thanks. I passed the source files through pgindent and attached the revised
patch. Although the arguments in the second line are not in line with the
first line's arguments, that's what pgindent found good.
Regards
MauMau
pg_ctl_eventsr
e made the attached patch. This prevents
unnecessary WAL accumulation in pg_xlog/ during archive recovery (not
standby recovery). To do this, I had to revive some code in
exitArchiveRecovery() from 9.1.
Could you commit this to 9.2 and later?
Regards
MauMau
wal_increase_in_pitr.patch
D
ssion is established.
Regards
MauMau
no_localize_message_in_startup.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
ocessing
out of the scope of pg_stat_statements?
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
best place. This could eliminate duplicate default values
in four places: pgevent.c, pg_ctl.c, elog.c, and guc.c. Thanks to your
review and comment, the code got cleaner and correct. Thank you very much.
Regards
MauMau
pg_ctl_eventsrc_v2.patch
Description: Binary data
--
Sent via pgsql-hacke
earest:
LOG
Reports information of interest to administrators, e.g., checkpoint
activity.
So, I thought "ereport(LOG, ...); proc_exit(0)" is more appropriate than
ereport(FATAL, ...). Is this so strange?
Regards
MauMau
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgre
From: "Andres Freund"
On 2013-12-12 00:31:25 +0900, MauMau wrote:
5. FATAL: terminating walreceiver process due to administrator command
6. FATAL: terminating background worker \"%s\" due to administrator
command
Those are important if they happen outside a shutdow
he reason is that connection options take effect in PostgresMain(), which
is after checking the FATAL condition in ProcessStartupPacket(). Do you
think there is any good solution?
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
due to administrator command
These are output when the DBA shuts down the database server and there's no
client connection. That is, these don't meet the criteria. I believe these
should be suppressed, or use LOG instead of FATAL.
Regards
MauMau
--
Sent via pgsql-hacke
101 - 200 of 369 matches
Mail list logo
