do option a. But how about option b?
2017-03-12 19:20 GMT+08:00 Michael Paquier :
> On Sun, Mar 12, 2017 at 5:24 PM, Jinhua Luo wrote:
>> I think this diverge scenario is common, because it's likely the
>> master would crash due to some hardware issue (e.g. power off) which
committed transaction has not yet synced to slave,
while the slave would be promoted to new master and accepts new
transactions, then how to recover the old master? Moreover, how to
recover the data on old master which is missing on new master?
Regards,
Jinhua Luo
--
Sent via pgsql-hackers ma
them into
the plpython function. The new thread would be pause and seems freeze
(as said above, I even try to put a dead loop in the thread, it
doesn't run a dead loop actually).
So I guess it's somehow plpython specific limit?
Regards,
Jinhua Luo
2016-02-08 0:45 GMT+08:00 Tom Lane
ering whether plpython supports threading or not.
Regards,
Jinhua Luo
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
cutorRun+0xfc/0x160
0x82d0503 : PortalRunSelect+0x183/0x200
0x82d17da : PortalRun+0x26a/0x3c0
0x82cf452 : PostgresMain+0x2282/0x2fc0
0x8097f52 : ServerLoop+0xb1b/0xec2
0x82793d7 : PostmasterMain+0x1237/0x13c0
0x8098b6c : main+0x48c/0x4d4
0xb754fa83 : __libc_start_main+0xf3/0x210
0x8098bd5 : _star
oing the same thing (there is no HOT
updates, obviously), but why some updated rows are reported by
heap_page_prune() but the others are not? And it's also a random
issue. That means sometimes heap_page_prune() would report all
removable rows, and sometimes it reports no rows.
Regards,
Jinhua
han actual rows, and the n_tup_upd is even
bigger than n_tup_ins!
Regards,
Jinhua Luo
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
2016-01-23 23:00 GMT+08:00 Tom Lane :
> Jinhua Luo writes:
>> I have a table with 70 columns, and 6 indexes. The data flow is a
>> special OLTP model: frequent inserts (2000 tps), and each inserted row
>> would be updated very soon (i.e. the number of inserts is equal to the
t a value for vacuum_defer_cleanup_age?
>
No, I do not configure it.
Regards,
Jinhua Luo
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
ycled and count in the fsm, right? I
just cannot understand why the recycle ratio is not 50%.
Regards,
Jinhua Luo
2016-01-23 15:13 GMT+08:00 Amit Kapila :
> On Sat, Jan 23, 2016 at 12:13 PM, Jinhua Luo wrote:
>>
>> Hi All,
>>
>> Here is my test environment:
>>
&g
nonremovable rows is just a
small fraction. If it's true, then no wonder that the table would keep
extending for a long time, because the free space is almost small.
Why the free space after vacuum is not 50% of the original size in my case?
Please help. Thanks!
Regards,
Jinhua Luo
--
11 matches
Mail list logo
