OK.
I've started working on the PostgreSQL-KNOPPIX English version.
Could anyone tell me postgresql related events schedule?
Are OSCON(June, Portland) and LinuxWorld(August, San Francisco) nearest?
Josh Berkus [EMAIL PROTECTED] wrote:
Jean-Michel,
Morphix is an auto-bootable Debian
Oops. Sorry I missed that thread.
(Because I was working on my master thesis...)
I'll read the past msgs before coming back this topic.
Marc G. Fournier [EMAIL PROTECTED] wrote:
On Sat, 24 Jan 2004, Satoshi Nagayasu wrote:
OK.
I've started working on the PostgreSQL-KNOPPIX English version
, languages, user
apps) should be included?
Any suggestions or recommendations?
No Starch Press's KNOPPIX includes all of server-side stuffs, pgAdmin3
and pgaccess. Right?
Satoshi Nagayasu [EMAIL PROTECTED] wrote:
Oops. Sorry I missed that thread.
(Because I was working on my master thesis...)
I'll
I and some other developers are also interested in.
Do you think we can work together?
Tatsuo Ishii [EMAIL PROTECTED] wrote:
Has this been beaten to death now? Just curious if PITR was in Dev tree
yet. Been out of the loop. TIA.
I and my co workers are very interested in implementing PITR.
I and some other developers are also interested in.
Do you think we can work together?
Tatsuo Ishii [EMAIL PROTECTED] wrote:
Has this been beaten to death now? Just curious if PITR was in Dev tree
yet. Been out of the loop. TIA.
I and my co workers are very interested in implementing PITR.
Darren Johnson [EMAIL PROTECTED] wrote:
I would like to here more about your implementation. Do you have some
documentation that I
could read?
Documentation is not available, but I have some slides for my presentation.
http://snaga.org/pgsql/20021018_2pc.pdf
Some answers for your
Tom Lane wrote:
I don't see why 2PC would require any protocol-level change. I would
think that the API would be something like
BEGIN;
issue some commands ...
PRECOMMIT;
-- if the above does not return an error, then
COMMIT;
In other words, 2PC would
Hi,
Mike Mascari [EMAIL PROTECTED] wrote:
Is there any thought about changing the protocol to support
two-phase commit? Not that 2PC and distributed transactions
would be implemented in 7.4, but to prevent another protocol
change in the future?
I'm now implementing 2PC replication and
Hannu Krosing [EMAIL PROTECTED] wrote:
I think a precommit-vote-commit phase of 2PC can be implemented in
command-lavel or protocol-level.
In command-level 2PC, an user application (or application programmer)
must know the DBMS is clustered or not (to use PRECOMMIT command).
In
Ross J. Reedstrom [EMAIL PROTECTED] wrote:
If application continues to use just BEGIN/COMMIT, then the protocol
level must parse command stream and recognize COMMIT in order to replace
it with PRECOMMIT, COMMIT.
If the communication library has to do that anyway, it could still
Hannu Krosing [EMAIL PROTECTED] wrote:
Exactly. When user send the COMMIT command to the master server, the
master.talks to the slaves to process precommit-vote-commit using the
2PC. The 2PC cycle is hidden from user application. User application
just talks the normal FE/BE protocol.
Ross J. Reedstrom [EMAIL PROTECTED] wrote:
Because the postgres backend must detect a type of incomming connection
(from the client app or the master).
If it is comming from the client, the backend relays the queries to the
slaves (act as the master).
But if it is comming from
Hi all,
Mike Mascari [EMAIL PROTECTED] wrote:
Is there any thought about changing the protocol to support
two-phase commit? Not that 2PC and distributed transactions
would be implemented in 7.4, but to prevent another protocol
change in the future?
I'm now implementing 2PC replication and
Michael Meskes [EMAIL PROTECTED] wrote:
Unfortunately it doesn't always work this way. I knew one government
organization that decided to go for Oracle for 500K Euro instead of
adding the missing features (actually almost exclusively PITR). One of
the top arguments I heard was: I don't
Hi all,
I'm hacking on PalmOS handhelds to implements libpq
called libpq for PalmOS.
This library provides many compatible libpq functions
to manipulate PostgreSQL server from PalmOS devices
through TCP/IP connection.
Implementation is almost done, but some works are left
to release.
For
Hi all,
In 7.2.1, MasterInit script (rserv command) does not work correctly,
because $libdir is not defined in it.
I think $libdir should be replaced in Makefile as below.
Is it correct?
--- MakefileMon Mar 11 13:39:14 2002
+++ /tmp/Makefile Tue Aug 13 18:19:21 2002
@@ -22,10 +22,10
Hello all,
I've created a lock timeout patch and it's attached.
When a transaction is blocked by another transaction because of
waiting a lock, we need a lock timeout in some cases.
Using this patch, the lock timeout is enabled with
'lock_timeout = ' directive in postgresql.conf,
and if a
function.
Tom Lane wrote:
Satoshi Nagayasu [EMAIL PROTECTED] writes:
When a transaction is blocked by another transaction because of
waiting a lock, we need a lock timeout in some cases.
Isn't there an existing solution for this problem?
regards, tom lane
statement_timeout terminates large sort or scan
even if it is running, doesn't it?
statement_timeout doesn't care that
the process is waiting a lock or running.
I don't want to terminate a running query.
So a lock waiting backend shold be killed.
Tom Lane wrote:
Satoshi Nagayasu [EMAIL
Tom Lane wrote:
I'd accept a mechanism to enforce a timeout at the lock level if you
could show me a convincing use-case for lock timeouts instead of
statement timeouts, but I don't believe there is one. I think this
proposal is a solution in search of a problem.
I think statement_timeout
Robert Treat wrote:
I think statement_timeout and lock_timeout are different.
If I set statement_timeout to 1000 to detect a lock timeout,
I can't run a query which takes over 1 sec.
If a lock wait is occured, I want to detect it immediately,
but I still want to run a long-running query.
How
Dennis Bjorklund wrote:
If I set statement_timeout to 1000 to detect a lock timeout,
I can't run a query which takes over 1 sec.
If a lock wait is occured, I want to detect it immediately,
but I still want to run a long-running query.
Why is it important what it is that makes your query not
Hello all,
A few days ago, I found that CREATE OR REPLACE TRIGGER
is not allowed on 7.4.2. However, functions and rules allow
CREATE OR REPLACE statement.
Is threre any reason not to support CREATE OR REPLACE
only for triggers?
Thanks.
--
NAGAYASU Satoshi [EMAIL PROTECTED]
OpenSource
And how often do you need to redefine a trigger (as opposed to its
underlying function), anyway?
I just want to know why not supported.
It's not a serious problem.
Tom Lane wrote:
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
Is threre any reason not to support CREATE OR REPLACE
only
Hello all,
I'm now working on performance tuning for PostgreSQL application.
I know shared_buffers and sort_mem have huge impacts for the performance.
If a disk sort (called tape sort in the code) is occured, we need to
increase sort_mem value. Then I found it is difficult to get a
reasonable
Hello all,
I'm trying to modify the storage manager now.
I found a number of smgrs are stored separately in the storage manager
module (NSmgr in smgr.c and NStorageManagers in smgrtype.c),
and names of storage managers are stored in smgrtype.c.
Are there any reason for this?
I think they shold
I'm trying to modify the storage manager now.
Um ... why?
Because I want to add my new storage manager.
It is not just for (single) magnetic disk.
If anyone had wanted to add a new storage manager in the last fifteen
years, we'd doubtless have tried to clean this up some, but no one has
How about enable/disable triggers?
From TODO:
Allow triggers to be disabled.
http://momjian.postgresql.org/cgi-bin/pgtodo?trigger
I think this is good for COPY performance improvement.
Now I have user functions to enable/disable triggers, not DDL.
It modifies system tables.
But I can rewrite
Bruce,
I have another patch for the TODO item.
From TODO item:
Add ability to monitor the use of temporary sort files
As I mentioned before, I created a sort statistics patch.
http://archives.postgresql.org/pgsql-hackers/2004-09/msg00380.php
Now my patch can work with 7.4.6 and it creates
Tom Lane wrote:
Josh Berkus josh@agliodbs.com writes:
Satoshi,
sort=# select * from pg_stat_sorts ;
� datname �| heap_all | index_all | heap_tape | index_tape | max_size
Good for me, if you explain the column names?
I was wondering about that too ... temporary sort files haven't got
Tom Lane wrote:
My patch counts inittapes(), tuplesort_begin_heap() and
tuplesort_begin_index(), and collect them, and sum them through the
stat collector.
Hm, that doesn't seem like quite the right level to be counting at.
Shouldn't you be hacking fd.c to count operations on
The TODO item is about counting all temporary files, not sorts in
particular. Or at least that's what I thought it meant.
If the DBA have to improve the performance,
DBA will need to know about:
- Which SQL generate a disk sort?
- Size of sorts.
- Changing 'work_mem' value can reduce
Hi all,
I've done a quick hack to implement PCTFREE on PostgreSQL.
As you know, it's inspired by Oracle's PCTFREE.
http://www.csee.umbc.edu/help/oracle8/server.815/a67772/schema.htm#990
http://www.comp.hkbu.edu.hk/docs/o/oracle10g/server.101/b10743/cncpt031.gif
Pre-allocated space for each
Tom Lane wrote:
I'm not very enthused about this. Enforcing 12.5% PCTFREE means that
you pay 12.5% extra I/O costs across the board for INSERT and SELECT
and then hope you can make it back (plus some more) on UPDATEs.
pgbench is a completely UPDATE-dominated benchmark and thus it makes
such
Tom Lane wrote:
Jim C. Nasby [EMAIL PROTECTED] writes:
... But I agree with Satoshi; if there are
people who will benefit from this option (which doesn't hurt those who
choose not to use it), why not put it in?
Because there's no such thing as a free lunch. Every option we support
costs
Josh Berkus wrote:
Satoshi, if you can package up a patch on current CVS, I'll throw it at DBT2.
Ok. I'll do it.
--
NAGAYASU Satoshi [EMAIL PROTECTED]
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
Satoshi Nagayasu wrote:
Josh Berkus wrote:
Satoshi, if you can package up a patch on current CVS, I'll throw it at DBT2.
Ok. I'll do it.
I've created a new patch which can be applied to the current cvs tree.
http://dpsql.sourceforge.net/pctfree.cvs.diff
--
NAGAYASU Satoshi [EMAIL
Simon Riggs wrote:
The summary was:
1. Have a PCTFREE column added on a table by table basis
I think a good place to keep PCTFREE value is a new column
in the pg_class, and ALTER TABLE should be able to change this value.
2. Apply PCTFREE for Inserts only
3. Allow Updates to use the full
Simon Riggs wrote:
4. Allow to repair fragmentation in each page.
Because updates cause fragmentation in the page.
So we need to keep large continuous free space in each page,
if we want to get more effective on PCTFREE feature.
...doesn't VACUUM already do that?
VACUUM generates a huge
Magnus,
Magnus Hagander wrote:
It should be fairly easy to write a LDAP backend to password
authentication using openldap, winldap or whatever ldap library is
available.
Before I start working on anything I'd like to check if a patch for this
would be accepted?
Also I was thinking about LDAP
Josh Berkus wrote:
And I want to get statistic info through system views, like pg_statio_*.
I don't think anyone disagrees with that. It's just a little too late to
get in for 8.1.
Thanks for comment. I hope 8.2 will get it.
--
NAGAYASU Satoshi [EMAIL PROTECTED]
Hi all,
karen hill wrote:
What do you see for 8.2 and beyond? What type of
features are you devs planning for 9.0? It would be
good if you could put up a place on your site so we
mortals can drool over up-coming postgresql features.
I'm wishing
- more audit facilities
-
Hi all,
(B
(BI'm thinking about "partial (or range) vacuum" feature.
(B
(BAs you know, vacuum process scans and re-organizes a whole table,
(Bso huge cpu load will be generated when vacuuming a large table,
(Band it will take long time (in some cases, it may take 10 minutes
(Bor more).
(B
(BTom Lane wrote:
(B I think the major problem with this is the (untenable) assumption that
(B the user is keeping track of the table size accurately. It'd be very
(B likely that portions of the table get missed if someone tries to
(B maintain a table using only partial vacuums specified in
Hi all,
(B
(BI've read TODO list in the 8.0.1,
(Bthen I'm interested in the following topic.
(B
(B * Allow a warm standby system to also allow read-only queries
(B
(BDoes anyone have any plan to work on this?
(B
(BI think we need to extend the pg_database catalog to
(Bhave a database
Tom Lane wrote:
(B Uh, no, because changing that would by definition not be a read-only
(B operation. Therefore there'd be no way to enter the read-only state,
(B and definitely no way to get out of it again.
(B
(BI saw Oracle's reference manual, and found ALTER DATABASE OPEN READ ONLY
Tom Lane wrote:
(BI saw Oracle's reference manual, and found ALTER DATABASE OPEN READ ONLY
(Bcommand
(Bto make a stand-by database.
(B
(B Perhaps, but that's *not* what the TODO item is about.
(B
(BI see.
(B
(BThanks for comments.
(B--
(BNAGAYASU Satoshi [EMAIL PROTECTED]
(BTom Lane wrote:
(B I'd view this as a postmaster state that propagates to backends.
(B Probably you'd enable it by means of a postmaster option, and the
(B only way to get out of it is to shut down and restart the postmaster
(B without the option.
(B
(BI've created a patch to make a
I'm using systable_beginscan() with TriggerConstrNameIndex
(Band systable_getnext().
(B
(BBTW, which value are you using as the cacheId
(Bwhen you call SearchSysCache() for pg_trigger?
(B
(BI couldn't find a suitable value in syscache.h.
(B
(Brafaqat ali wrote:
(B Hello All
(B
Bob wrote:
(B One simple benefit to packages is just organization of related code.
(B
(BAnd the package-scoped variables or constant values, similar to
(Bthe global variables.
(B
(BIt will be very useful for application programmers
(Bif one variable can be shared from several functions.
(B
Hi all,
(B
(BI'm now interested in audit facilities for database accessing.
(BAre anyone thinking or working on audit stuffs?
(B
(B--
(BNAGAYASU Satoshi [EMAIL PROTECTED]
(BOpenSource Development Center,
(BNTT DATA Corp. http://www.nttdata.co.jp/
(B
(B---(end of
Hiroshi Saito wrote:
(B http://archives.postgresql.org/pgsql-general/2004-08/msg01439.php
(B I remember that the approach which he enjoyed was being done.
(B
(BThanks for the information.
(B
(B However, I hope variously as a function of the PostgreSQL core.
(B
(BI hope they goes into the
Finally, I found the tablelog project at the pgFoundary...
(B
(Bhttp://pgfoundry.org/projects/tablelog/
(B
(BSatoshi Nagayasu wrote:
(B Hiroshi Saito wrote:
(B
(Bhttp://archives.postgresql.org/pgsql-general/2004-08/msg01439.php
(BI remember that the approach which he enjoyed was being
Hi all,
Josh's talk is now available at:
http://snaga.org/01_Josh_Berkus.mp3
This file is very long, and an interpreter's voice
to interpret into Japanese is also recorded.
If you want to learn Japanese, please try it! :)
Thanks.
Luke Lonergan wrote:
Drink Sake and eat some Yakitori for us
Hi all,
When I was playing with VACUUM, I found that if I have prepared xacts
on the database A, I can't vacuum full on the database B.
Scenario:
1.) Prepare some transaction on testdb database.
2.) Create database pgbench.
3.) Run pgbench -i to load pgbench data on pgbench database
4.) Delete
On 2/20/06, Tom Lane [EMAIL PROTECTED] wrote:
A prepared xact is the same as an open xact as far as vacuum is
concerned. It's a bad idea to sit on either open or prepared xacts
for long periods ...
I completely understand that, however it can be occured...
Prepared xacts never die...
I
Tom,
Luke Lonergan wrote:
I figure I can back it up...). What would people like to hear about?
How about future plans, so to speak? You've made some pretty significant
improvements for 8.1 (virtual tuples, the caching algorithm, etc), what's on
deck for 8.2 and beyond?
I'm *really*
Josh,
Josh Berkus wrote:
I've heard a couple other requests for dealing with vaccuum. I think a
Fixing Vacuum Round-Table might be a valuable session if we have someone to
lead it. You ready?
If required. I want to know how people think about vacuum, and
many ideas around vacuum.
To be
Oleg,
Refer to the Josh's past talk, PostgreSQL Directions 8.1 and beyond.
MP3 and materials of are available:
http://www.postgresql.jp/misc/seminar/2006-02-17_18/materials/01_Josh_Berkus.pdf
http://www.postgresql.jp/misc/seminar/2006-02-17_18/materials/01_Josh_Berkus.mp3
Thanks,
Satoshi
Tom Lane wrote:
In particular, asking for a list of features that will be done in
particular future releases shows a complete lack of understanding
of the process ...
I completely understand.
However, we also need to know why business people want
to know about the future plan. For the
Jim C. Nasby wrote:
Structure for the human-consumable output or for something that would be
machine-parsed? ISTM it would be best to keep the current output as-is,
and provide some other means for producing machine-friendly output,
presumably in a table format.
How about (well-formed) XML
Alvaro Herrera wrote:
Satoshi Nagayasu wrote:
Jim C. Nasby wrote:
Structure for the human-consumable output or for something that would be
machine-parsed? ISTM it would be best to keep the current output as-is,
and provide some other means for producing machine-friendly output,
presumably
[EMAIL PROTECTED] (monu agrawal) wrote:
Hi
I have developed a new buffer policy for biological databases, I want
to implement it on postgresql.So I will have to buffer manager of
pgsql.How should I do it?
Which files I will have to change what type of changes I will have
to make.
Very
Andrew Sullivan [EMAIL PROTECTED] wrote:
On Fri, Oct 10, 2003 at 09:46:35AM +0900, Tatsuo Ishii wrote:
Satoshi, the only guy who made a trial implementation of 2PC for
PostgreSQL, has already showed that 2PC is not that slow.
If someone has a fast implementation, so much the better. I'm
.
---
Satoshi Nagayasu wrote:
Andrew Sullivan [EMAIL PROTECTED] wrote:
On Fri, Oct 10, 2003 at 09:46:35AM +0900, Tatsuo Ishii wrote:
Satoshi, the only guy who made a trial implementation of 2PC for
PostgreSQL, has already showed that 2PC is not that slow
Hi folks,
I'm trying to use PAM auth on PostgreSQL, but I still cannot
get success on PAM auth (with PG813 and RHEL3).
pg_hba.conf has
hostpamtest all 0.0.0.0/0 pam
/etc/pam.d/postgresql is
#%PAM-1.0
auth required pam_stack.so service=system-auth
Albe,
Albe Laurenz wrote:
/etc/pam.d/system-auth probably uses pam_unix.so to authenticate.
Does the user exist on the machine and have the password you try?
Yes, I have same user name on my linux box and postgresql,
and they have same password (now).
You could add 'debug' to the
Andrew Dunstan wrote:
don't use system auth. PAM can authenticate from many sources, not just
the system password files. LDAP is a commonly used source.
The reason why I'm trying to use PAM, is I need a feature
to account lock-out after N-times login failures on PG,
like pam_tally module.
I'm
Tom,
Tom Lane wrote:
IOW pljava is (already) bigger than the other four PLs put together.
I'm inclined to think that pljava is best off staying as a separate
project.
I was very confused some recent PL/Java versions can't be compiled
because of PostgreSQL internal changes.
If people think
Kris Jurka wrote:
On Thu, 13 Jul 2006, Tom Lane wrote:
The people who think PL/Java is an essential checklist item
undoubtedly also think JDBC is an essential checklist item, but I'm
not seeing any groundswell of support for putting JDBC back into
core. Instead we expect packagers
Hi folks,
As I said on -PATCHES, I've been working on an utility to get
a b-tree index information. I'm happy to introduce
my new functions to you.
pgstattuple module provides a `pgstatindex()`, and other small
functions, which allow you to get b-tree internal information.
I believe this module
.
---
satoshi nagayasu wrote:
Hi folks,
As I said on -PATCHES, I've been working on an utility to get
a b-tree index information. I'm happy to introduce
my new functions to you.
pgstattuple module provides a `pgstatindex()`, and other small
ITAGAKI Takahiro wrote:
But the method has the above problem. So I suggest to use whether
the right link points to the next adjacent page or not.
if (opaque-btpo_next != P_NONE opaque-btpo_next != blkno + 1)
stat-fragments++;
Well, in that way, following two conditions,
[1]
ITAGAKI Takahiro wrote:
Satoshi Nagayasu [EMAIL PROTECTED] wrote:
Well, in that way, following two conditions,
[1] [x] [2] [y] [3]
and
[3] [x] [2] [y] [1]
will be calculated as same fragmentation ratio(100%), I can't agree
with that, because both will generate different costs while
ITAGAKI Takahiro wrote:
Suppose a simple update case, for example, the accounts table in pgbench.
The default fillfactor of btree indexes is 90%, so the leaf pages are
fully split after we update 10-20% of tuples. But pgstatindex reports
the fragmentation is 50% in such condition, but I think
Tom Lane wrote:
gcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline
-Wdeclaration-after-statement -Wendif-labels -fno-strict-aliasing -g -fpic
-I. -I../../src/include -D_GNU_SOURCE -c -o pgstatindex.o pgstatindex.c
pgstatindex.c: In function 'bt_page_items':
pgstatindex.c:564:
Tom,
Yes. It's pure overhead with no redeeming social value except to those
who actually want to look at that sort of stat, and those who do can
certainly turn it on for themselves.
I think the stats stuff should be on by default even if it causes
some performance penalty.
Because when we
Mark,
Very interesting. I'm looking for such tool.
Unfortunately, I can't compile it on my Solaris right now,
but I hope it will be shipped with PostgreSQL distribution.
Mark Wong wrote:
Hi everyone,
I was playing with converting unixtop (the version of top used in
FreeBSD) to only show
2012/01/11 19:56, Simon Riggs wrote:
2012/1/11 Euler Taveira de Oliveiraeu...@timbira.com:
On 08-01-2012 11:59, Satoshi Nagayasu / Uptime Technologies, LLC. wrote:
[2011-12-08 15:14:36 JST] 16758: LOG: restored log file
00080046 from archive
[2011-12-08 15:14:36 JST] 16758
about this one?
LOG: XXX file(s) from archive, YYY file(s) from pg_xlog successfully
applied.
Thanks,
--
Satoshi Nagayasu sn...@uptime.jp
Uptime Technologies, LLC. http://www.uptime.jp
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
(2012/11/27 7:42), Alvaro Herrera wrote:
Satoshi Nagayasu escribió:
I attached the latest one, which splits the reset_time
for bgwriter and walwriter, and provides new system view,
called pg_stat_walwriter, to show the dirty write counter
and the reset time.
Thanks. I gave this a look and I
(2012/12/10 3:06), Tomas Vondra wrote:
On 29.10.2012 04:58, Satoshi Nagayasu wrote:
2012/10/24 1:12, Alvaro Herrera wrote:
Satoshi Nagayasu escribi�:
With this patch, walwriter process and each backend process
would sum up dirty writes, and send it to the stat collector.
So, the value could
the upper bound of int when sf21474.)
Also, I added a few fixes on it.
- Fixed to apply for the current git master.
- Fixed to surpress few more warnings about INT64_FORMAT.
- Minor improvement in the docs. (just my suggestion)
I attached the revised one.
Regards,
--
Satoshi Nagayasu sn
.
Then, I need some suggestion from hackers to continue this review.
How should I reproduce this message for review?
This is a debug warning message, so it's not easy for me
to reproduce this message.
Any suggestion?
--
Satoshi Nagayasu sn...@uptime.jp
Uptime Technologies, LLC http
support.
It seems working well with the latest git master.
I think it's good enough to be committed.
BTW, is there any good place to put new regression test for the psql
command? I couldn't find it out.
Any comment or suggestion?
Regards,
--
Satoshi Nagayasu sn...@uptime.jp
Uptime Technologies
(2013/01/30 0:34), Tom Lane wrote:
Satoshi Nagayasu sn...@uptime.jp writes:
On Mon, 2013-01-07 at 07:14 -0500, Peter Eisentraut wrote:
Here is a patch for psql's \l command to accept patterns, like \d
BTW, is there any good place to put new regression test for the psql
command? I couldn't
=# SELECT pg_stat_get_xlog_dirty_write();
pg_stat_get_xlog_dirty_write
--
0
(1 row)
postgres=# \q
[snaga@devvm03 src]$
---
--
Satoshi Nagayasu sn...@uptime.jp
Uptime Technologies, LLC. http
2012/07/07 22:07, Euler Taveira wrote:
On 07-07-2012 09:00, Satoshi Nagayasu wrote:
I've created new patch to get/reset statistics of WAL buffer
writes (flushes) caused by WAL buffer full.
This new statistic doesn't solve your problem (tune wal_buffers). It doesn't
give you the wal_buffers
into
the shared memory, as a member of XLogCtlWrite, to keep total
dirty writes in the cluster.
Regards,
2012/07/07 21:00, Satoshi Nagayasu wrote:
Hi all,
I've created new patch to get/reset statistics of WAL buffer
writes (flushes) caused by WAL buffer full.
This patch provides two new functions
older major version could not take
advantage of new features and enhancements of the latest xlogdump,
but it's not what I wanted, actually.
Regards,
Greetings,
Andres
--
Satoshi Nagayasu sn...@uptime.jp
Uptime Technologies, LLC. http://www.uptime.jp
--
Sent via pgsql-hackers mailing list
,
--
Satoshi Nagayasu sn...@uptime.jp
Uptime Technologies, LLC. http://www.uptime.jp
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
?
Regards,
--
Satoshi Nagayasu sn...@uptime.jp
Uptime Technologies, LLC. http://www.uptime.jp
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
allocation strategy for some usages
still seems like something we'll want to do someday, though.
regards, tom lane
--
Satoshi Nagayasu sn...@uptime.jp
Uptime Technologies, LLC. http://www.uptime.jp
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org
development
and enough eyeballs to maintain, it's ok to be an independent project.
However when a tool have already got matured with less eyeballs,
it needs to be merged into this umbrella project.
Any comments?
Sakamoto
--
Satoshi Nagayasu sn...@uptime.jp
Uptime Technologies, LLC. http
]$
--
Satoshi Nagayasu sn...@uptime.jp
Uptime Technologies, LLC. http://www.uptime.jp
diff --git a/src/interfaces/libpq/fe-connect.c
b/src/interfaces/libpq/fe-connect.c
index 9eaf410..14e31b6 100644
--- a/src/interfaces/libpq/fe-connect.c
+++ b/src/interfaces/libpq/fe-connect.c
@@ -569,6 +569,81
PGP SIGNATURE-
--
Satoshi Nagayasu sn...@uptime.jp
Uptime Technologies, LLC. http://www.uptime.jp
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
and again, it's time to consider
implementing it to deliver and/or leverage with the potential
of PostgreSQL replication.
Regards,
On 2012-09-23 10:01 AM, Euler Taveira eu...@timbira.com
mailto:eu...@timbira.com wrote:
On 23-09-2012 07:50, Satoshi Nagayasu wrote:
I have just written
.
AFAIK, basically, rebuilding tables and/or indexes has
a trade-off between lock-free and disk-space.
So, if we have enough disk space to build a temporary
table/index when rebuilding a table/index, concurrently
would be a great option, and I would love it to have
in core.
Regards,
--
Satoshi
Hi,
2012/08/12 7:11, Jeff Janes wrote:
On Sat, Jul 28, 2012 at 3:33 PM, Jeff Janes jeff.ja...@gmail.com wrote:
On Sat, Jul 7, 2012 at 9:17 PM, Satoshi Nagayasu sn...@uptime.jp wrote:
Hi,
Jeff Janes has pointed out that my previous patch could hold
a number of the dirty writes only in single
.
pg_stat_reset_lwlocks() New function to reset lwlock statistics.
Please try it out.
Regards,
2012/06/26 5:29, Satoshi Nagayasu wrote:
Hi all,
I've been working on a new system view, pg_stat_lwlocks, to observe
LWLock, and just completed my 'proof-of-concept' code that can work
1 - 100 of 177 matches
Mail list logo
