Re: [HACKERS] crash-safe visibility map, take four

> > > All operations that clear the bit area are already WAL-logged. > > Is it the case with visibility map also? Thanks.

Re: [HACKERS] crash-safe visibility map, take four

On 2011-03-22 21:43, Robert Haas wrote: I took a crack at implementing the first approach described above, which seems to be by far the simplest idea we've come up with to date. Patch attached. It doesn't seem to be that complicated, which could mean either that it's not that complicated or th

Re: [HACKERS] pg_ctl restart - behaviour based on wrong instance

On Sat, Mar 19, 2011 at 10:20 AM, Robert Haas wrote: > On Fri, Mar 18, 2011 at 1:19 PM, Erik Rijkers wrote: >> This is OK and expected.  But then it continues (in the logfile) with: >> >> FATAL:  lock file "postmaster.pid" already exists >> HINT:  Is another postmaster (PID 20519) running in data

Re: [HACKERS] crash-safe visibility map, take four

On Tue, Mar 22, 2011 at 11:59 PM, Gokulakannan Somasundaram wrote: >> I took a crack at implementing the first approach described above, >> which seems to be by far the simplest idea we've come up with to date. >>  Patch attached.  It doesn't seem to be that complicated, which could >> mean either

Re: [HACKERS] crash-safe visibility map, take four

> > I took a crack at implementing the first approach described above, > which seems to be by far the simplest idea we've come up with to date. > Patch attached. It doesn't seem to be that complicated, which could > mean either that it's not that complicated or that I'm missing > something. Feel

[HACKERS] writing a script to examine dead tuples

Can anyone help me, i am trying to carry out an investigation which involves accessing dead tuples within the postgresql. I have been advised i could write a script that allows me to examine dead tuples and am seeking advise on how to achieve this, or pointers that can help me going in the right

[HACKERS] writing a script to examine dead tuples

Can anyone help me, i am trying to carry out an investigation which involves accessing dead tuples within the postgresql. I have been advised i could write a script that allows me to examine dead tuples and am seeking advise on how to achieve this, or pointers that can help me going in the right

[HACKERS] Comments on SQL/Med objects

Hi, While working on adding support for SQL/Med objects to pgAdmin, I'm quite surprised to see there is no way to add comments to SQL/Med objects. Is this on purpose or is it just something that was simply missed? Thanks. -- Guillaume http://www.postgresql.fr http://dalibo.com -- Sent via

Re: [HACKERS] 2nd Level Buffer Cache

On Tue, Mar 22, 2011 at 4:28 PM, Radosław Smogura wrote: > Merlin Moncure Monday 21 March 2011 20:58:16 >> On Mon, Mar 21, 2011 at 2:08 PM, Greg Stark wrote: >> > On Mon, Mar 21, 2011 at 3:54 PM, Merlin Moncure > wrote: >> >> Can't you make just one large mapping and lock it in 8k regions? I >>

Re: [HACKERS] pgsql: Throw error for indeterminate collation of an ORDER/GROUP/DISTIN

Greg Stark writes: > On Tue, Mar 22, 2011 at 7:58 PM, Tom Lane wrote: >> Throw error for indeterminate collation of an ORDER/GROUP/DISTINCT target. > hmm. In the current arrangement = doesn't depend on collation, right? I've been trying to get rid of that assumption where I could. I think it wo

Re: [HACKERS] pgsql: Throw error for indeterminate collation of an ORDER/GROUP/DISTIN

On Tue, Mar 22, 2011 at 7:58 PM, Tom Lane wrote: > Throw error for indeterminate collation of an ORDER/GROUP/DISTINCT target. > hmm. In the current arrangement = doesn't depend on collation, right? So in an ideal world we could use any collation we want to implement GROUP/DISTINCT/UNION/INTERSECT

Re: [HACKERS] Flex output missing from 9.1a4 tarballs?

Robert Haas writes: > On Tue, Mar 15, 2011 at 10:00 PM, Tom Lane wrote: >> FWIW, collations are probably still several days away from being >> noticeably less broken than they were in alpha4. > How much less broken are they now? I think the core code is only locally broken now, with issues like

Re: [HACKERS] Feature proposal: distinguish each PostgreSQL instance in the event log

I'm sorry that I've mistakenly sent an empty mail. This is the intended mail. "Andrew Dunstan" wrote in message news:4d889879.3080...@dunslane.net... On 03/22/2011 08:22 AM, MauMau wrote: I would appreciate your opinions and advice. I'll try making the patch while I'm waiting for response.

Re: [HACKERS] GSoC 2011 - Mentors? Projects?

Greetings, ADJ Dashboard project small description is written https://github.com/hzroot/ADJ-Dashboard/wiki here. If you give suggestions (what you need as a dba? or what you use most? etc.. ), it will be great! 22 Mart 2011 03:51 tarihinde Devrim GÜNDÜZ yazdı: > On Mon, 2011-03-14 at 16:08 +0

Re: [HACKERS] 2nd Level Buffer Cache

Merlin Moncure Monday 21 March 2011 20:58:16 > On Mon, Mar 21, 2011 at 2:08 PM, Greg Stark wrote: > > On Mon, Mar 21, 2011 at 3:54 PM, Merlin Moncure wrote: > >> Can't you make just one large mapping and lock it in 8k regions? I > >> thought the problem with mmap was not being able to detect ot

[HACKERS] crash-safe visibility map, take four

On Wed, Dec 1, 2010 at 11:25 AM, Robert Haas wrote: > As far as I can tell, there are basically two viable solutions on the > table here. > > 1. Every time we observe a page as all-visible, (a) set the > PD_ALL_VISIBLE bit on the page, without bumping the LSN; (b) set the > bit in the visibility m

Re: [HACKERS] Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.

On Fri, Mar 18, 2011 at 5:08 PM, Aidan Van Dyk wrote: > On Fri, Mar 18, 2011 at 3:41 PM, Markus Wanner wrote: >> On 03/18/2011 08:29 PM, Simon Riggs wrote: >>> We could do that easily enough, actually, if we wished. >>> >>> Do we wish? >> >> I personally don't see any problem letting a standby sh

Re: [HACKERS] Flex output missing from 9.1a4 tarballs?

On Tue, Mar 15, 2011 at 10:00 PM, Tom Lane wrote: > Robert Haas writes: >> 2011/3/15 Devrim GÜNDÜZ : >>> If you need more votes for this: +1 from me. I'd like to wrap the >>> packages before I leave for PGEast. > >> My only hesitation about this is that it seems like sync rep and >> collation sup

Re: [HACKERS] wrap alpha4 tomorrow ~9am Eastern (was: Alpha4 release blockers)

On Wed, Mar 9, 2011 at 11:04 PM, Josh Berkus wrote: > Should I write the announcement for this, or do you want to? For alpha4? I'd be happy for you to do it, but it's a bit out of date now. I was thinking to bundle alpha5 on Monday; maybe we should just wait and announce that one. -- Robert H

Re: [HACKERS] Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.

On Fri, Mar 18, 2011 at 3:41 PM, Markus Wanner wrote: > On 03/18/2011 08:29 PM, Simon Riggs wrote: >> We could do that easily enough, actually, if we wished. >> >> Do we wish? > > I personally don't see any problem letting a standby show a snapshot > before the master.  I'd consider it unneeded ne

Re: [HACKERS] Alpha4 release blockers (was Re: wrapping up this CommitFest)

Andres Freund writes: > On Saturday 05 March 2011 17:46:13 Tom Lane wrote: >> Andres Freund writes: * Collation-related regression failure on buildfarm member pika. This is clearly a bug we need to identify, but maybe we can ship the alpha without a fix --- for one thing, getting

Re: [HACKERS] wrap alpha4 tomorrow ~9am Eastern (was: Alpha4 release blockers)

Robert, Should I write the announcement for this, or do you want to? -- -- Josh Berkus PostgreSQL Experts Inc. http://www.pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hack

Re: [HACKERS] 2nd Level Buffer Cache

Radek, I have implemented initial concept of 2nd level cache. Idea is to keep some segments of shared memory for special buffers (e.g. indices) to prevent overwrite those by other operations. I added those functionality to nbtree index scan. The problem with any "special" buffering of database

Re: [HACKERS] 2nd Level Buffer Cache

On Tue, 2011-03-22 at 15:53 -0400, Robert Haas wrote: > > To be honest, I'm mostly just reporting what I've heard Greg Smith say > on this topic. I don't have any machine with that kind of RAM. I thought we had a machine for hackers who want to do performance testing. Mark? -- Devrim GÜNDÜZ P

Re: [HACKERS] 2nd Level Buffer Cache

On Tue, Mar 22, 2011 at 11:24 AM, Jeff Janes wrote: > On Fri, Mar 18, 2011 at 9:19 AM, Robert Haas wrote: >> On Fri, Mar 18, 2011 at 11:14 AM, Kevin Grittner >> wrote: >>> Maybe the thing to focus on first is the oft-discussed "benchmark >>> farm" (similar to the "build farm"), with a good mix o

Re: Sync Rep and shutdown Re: [HACKERS] Sync Rep v19

On Tue, Mar 22, 2011 at 3:25 PM, Yeb Havinga wrote: > So the patch eats 4,5% from git master's syncrep performance in my setup. > Don't know how to measure it better than that. That's quite surprising, but I guess the way forward is clear: don't apply that patch. -- Robert Haas EnterpriseDB: ht

Re: Sync Rep and shutdown Re: [HACKERS] Sync Rep v19

On 2011-03-21 23:58, Yeb Havinga wrote: On Mon, Mar 21, 2011 at 7:51 PM, Yeb Havinga > wrote: On 2011-03-21 18:04, Robert Haas wrote: On Mon, Mar 21, 2011 at 12:29 PM, Yeb Havingamailto:yebhavi...@gmail.com>> wrote: pgbench

Re: [HACKERS] VACUUM FULL deadlock with backend startup

> Patch applied, thanks! > > Thanks Tom! Regards, Nikhils

Re: [HACKERS] VACUUM FULL deadlock with backend startup

Nikhil Sontakke writes: > It looked familiar, so I dug up the archives and found that Tom had > committed a fix for a similar deadlock via git commitid: 715120e7 > However this current deadlock involved an index with oid 2663, which > is ClassNameNspIndexId. Clearly this was another case of locki

Re: [HACKERS] 2nd Level Buffer Cache

On 03/22/2011 12:47 PM, Jeff Janes wrote: Maybe the thing to focus on first is the oft-discussed "benchmark farm" (similar to the "build farm"), with a good mix of loads, so that the impact of changes can be better tracked for multiple workloads on a variety of platforms and configurations.

Re: [HACKERS] psql \dt and table size

2011/3/22 David Fetter : > +1 for fixing this behavior in 9.1.  -1 for changing in 9.0, as the > change in behavior mid-release will cause more confusion than the > incomplete accounting does. Idem. > > Cheers, > David. > On Mon, Mar 21, 2011 at 06:44:51PM +0100, Bernd Helmle wrote: >> It stroke

Re: [HACKERS] really lazy vacuums?

2011/3/22 Greg Stark : > On Mon, Mar 21, 2011 at 6:08 PM, Jim Nasby wrote: >> Has anyone looked at the overhead of measuring how long IO requests to the >> kernel take? If we did that not only could we get an idea of what our IO >> workload looked like, we could also figure out whether a block c

Re: [HACKERS] 2nd Level Buffer Cache

On Fri, Mar 18, 2011 at 8:14 AM, Kevin Grittner wrote: > rsmogura wrote: > >> Yes, there is some change, and I looked at this more carefully, as >> my performance results wasn't such as I expected. I found PG uses >> BufferAccessStrategy to do sequence scans, so my test query took >> only 32 buff

Re: [HACKERS] Feature proposal: distinguish each PostgreSQL instance in the event log

On 03/22/2011 11:35 AM, MauMau wrote: > I'm sorry that I've mistakenly sent an empty mail. This is the > intended mail. > > "Andrew Dunstan" wrote in message > news:4d889879.3080...@dunslane.net... >> >> On 03/22/2011 08:22 AM, MauMau wrote: >>> I would appreciate your opinions and advice. I'll

Re: [HACKERS] Feature proposal: distinguish each PostgreSQL instance in the event log

I'm sorry that I've mistakenly sent an empty mail. This is the intended mail. "Andrew Dunstan" wrote in message news:4d889879.3080...@dunslane.net... On 03/22/2011 08:22 AM, MauMau wrote: I would appreciate your opinions and advice. I'll try making the patch while I'm waiting for response.

Re: [HACKERS] When and where do PG invoke PLs module？

Em 21-03-2011 06:26, _ʯͷ escreveu: I've tried to find when and where do PG invoke PLs module,but failed.There are four procedures for a query string--parer, rewrite,plan and execute. I want to know which part invoke the PLs module,and which function is the entry to do that. Look at src/pl/foo an

Re: [HACKERS] 2nd Level Buffer Cache

On Fri, Mar 18, 2011 at 9:19 AM, Robert Haas wrote: > On Fri, Mar 18, 2011 at 11:14 AM, Kevin Grittner > wrote: >> Maybe the thing to focus on first is the oft-discussed "benchmark >> farm" (similar to the "build farm"), with a good mix of loads, so >> that the impact of changes can be better tra

Re: [HACKERS] Feature proposal: distinguish each PostgreSQL instance in the event log

"MauMau" writes: > I've encountered one problem on Windows. I need to support running all of my > products on one host simultaneously. Plus, I need to log messages in > syslog/event log. On Linux, I can distinguish the messages of one product > and those of other products by setting syslog_iden

Re: [HACKERS] Feature proposal: distinguish each PostgreSQL instance in the event log

-- 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] Feature proposal: distinguish each PostgreSQL instance in the event log

On 03/22/2011 08:22 AM, MauMau wrote: > Hello, > > I have several software products which use PostgreSQL as a data > repository and embed the same PostgreSQL binaries. Currently, those > software support Linux. I'm trying to port them to Windows. > > I've encountered one problem on Windows. I nee

[HACKERS] Feature proposal: distinguish each PostgreSQL instance in the event log

Hello, I have several software products which use PostgreSQL as a data repository and embed the same PostgreSQL binaries. Currently, those software support Linux. I'm trying to port them to Windows. I've encountered one problem on Windows. I need to support running all of my products on one

Re: [HACKERS] 2nd Level Buffer Cache

Hi, hackers. I am interested in this discussion! So I surveyed current buffer algorithms around other software. I share about it. (sorry, it is easy survey..) CLOCK-PRO and LIRS are popular in current buffer algorithms in my easy survey. Their algorithms are same author that is Song Jiang. CLOCK

Re: [HACKERS] Rectifying wrong Date outputs

Thanks Heikki, Tom & Robert for your valuable inputs. According to the code, PG is behaving what is mentioned below. 1. Format = Y 0 ... 9 = 2000 ... 2009 (we are always adding 2000 to the year) 2. Format = YY 00 ... 69 = 2000 ... 2069 (we are adding 2000 to the year) 70 ... 99 = 1970 ... 1999

Re: [HACKERS] Collations versus record-returning functions

On sön, 2011-03-20 at 20:26 +0100, Martijn van Oosterhout wrote: > A rowtype has an order, determined by the fields within it. Those > fields may be strings and so may have a collation. Doesn't seem > particularly magical to me. Yeah, that's answer #4. The composite types themselves are not consi

Re: [HACKERS] Chinese initdb on Windows

On 22.03.2011 01:06, Tom Lane wrote: Heikki Linnakangas writes: Any objections to the 2nd attached patch, which adds the mapping of those locale names on Windows? I think the added initdb message isn't following our style guidelines --- it certainly doesn't match the adjacent existing message

Re: [HACKERS] How to look at the Expression Trees

On 22.03.2011 05:39, Vaibhav Kaushal wrote: You said: ExecMakeFunctionResultNoSets is used to evaluate function calls. What are the 'functions' there? Are they the user supplied pl/PGSQL style user functions, the functions handled by fmgr or are they just another C function which make the Expre