On 19.08.2011 23:17, Robert Haas wrote:
On Fri, Aug 19, 2011 at 4:02 PM, Robert Haas wrote:
Hmm, you have a point. If 100 backends simultaneously write to 100
different pages, and all of those pages are all-visible, then it's
possible that they could end up fighting over the buffer content loc
On 19.08.2011 23:02, Robert Haas wrote:
On Fri, Aug 19, 2011 at 2:51 PM, Gokulakannan Somasundaram
wrote:
won't it make the 99
sessions wait for that visibility map while holding the exclusive lock on
the 99 heap pages?
Hmm, you have a point. If 100 backends simultaneously write to 100
diff
"Sergey E. Koposov" writes:
> But the funny thing I noticed is that the query after running a certain
> amount of time doing I/O, starts to use 100%CPU and spend 99% the time in
> hash_seq_search. Here is the oprofile of PG during that period:
>
> CPU: Intel Core/i7, speed 2.268e+06 MHz
On Fri, Aug 19, 2011 at 09:49:35PM -0400, Bruce Momjian wrote:
> David Fetter wrote:
> > On Fri, Aug 19, 2011 at 09:22:03PM -0400, Andrew Dunstan wrote:
> > > On 08/19/2011 09:02 PM, David Fetter wrote:
> > > >On Fri, Aug 19, 2011 at 07:37:29PM -0400, Andrew Dunstan wrote:
> > > >>
> > > >>On 08/19
On 08/19/2011 09:39 PM, David Fetter wrote:
Tie::File ships as part of core Perl for all non-EOL versions, so I
really can't consider this as a problem.
Which are those?
5.12 and 5.14 are still supported. 5.10 and earlier are EOL.
http://news.perlfoundation.org/2011/05/perl-514.html
We
David Fetter wrote:
> On Fri, Aug 19, 2011 at 09:22:03PM -0400, Andrew Dunstan wrote:
> > On 08/19/2011 09:02 PM, David Fetter wrote:
> > >On Fri, Aug 19, 2011 at 07:37:29PM -0400, Andrew Dunstan wrote:
> > >>
> > >>On 08/19/2011 07:31 PM, Bruce Momjian wrote:
> > >>>Kris Jurka wrote:
> > Did y
On Fri, Aug 19, 2011 at 09:22:03PM -0400, Andrew Dunstan wrote:
> On 08/19/2011 09:02 PM, David Fetter wrote:
> >On Fri, Aug 19, 2011 at 07:37:29PM -0400, Andrew Dunstan wrote:
> >>
> >>On 08/19/2011 07:31 PM, Bruce Momjian wrote:
> >>>Kris Jurka wrote:
> Did you also try the "use Tie::File" ad
On 08/19/2011 09:02 PM, David Fetter wrote:
On Fri, Aug 19, 2011 at 07:37:29PM -0400, Andrew Dunstan wrote:
On 08/19/2011 07:31 PM, Bruce Momjian wrote:
Kris Jurka wrote:
Did you also try the "use Tie::File" addition in my fix because your
current coding doesn't work at all. The tie operat
On Fri, Aug 19, 2011 at 07:37:29PM -0400, Andrew Dunstan wrote:
>
>
> On 08/19/2011 07:31 PM, Bruce Momjian wrote:
> >Kris Jurka wrote:
> >>Did you also try the "use Tie::File" addition in my fix because your
> >>current coding doesn't work at all. The tie operation is key to actually
> >>writin
On Fri, 19 Aug 2011, Bruce Momjian wrote:
> Andrew Dunstan wrote:
> >
> > It probably doesn't matter that much in this context, but I should point
> > out that Tie::File is not universally available. Some years ago I had to
> > revert its use in the buildfarm code for that reason. In general
Andrew Dunstan wrote:
>
>
> On 08/19/2011 07:31 PM, Bruce Momjian wrote:
> > Kris Jurka wrote:
> >> Did you also try the "use Tie::File" addition in my fix because your
> >> current coding doesn't work at all. The tie operation is key to actually
> >> writing out the modified copyright notice.
On 08/19/2011 07:31 PM, Bruce Momjian wrote:
Kris Jurka wrote:
Did you also try the "use Tie::File" addition in my fix because your
current coding doesn't work at all. The tie operation is key to actually
writing out the modified copyright notice. Your version just updates the
copyright year
Kris Jurka wrote:
>
>
> On Fri, 19 Aug 2011, Bruce Momjian wrote:
>
> > Was able to reproduce the error you reported with Perl 5.10. I then
> > tried the single-quote idea I got from Googling, but then got an error
> > about TIEARRAY being missing, so I recoded it as a simple file
> > open/clos
On Fri, 19 Aug 2011, Bruce Momjian wrote:
> Was able to reproduce the error you reported with Perl 5.10. I then
> tried the single-quote idea I got from Googling, but then got an error
> about TIEARRAY being missing, so I recoded it as a simple file
> open/close. I also incorported your regex
Kris Jurka wrote:
>
>
> On Fri, 19 Aug 2011, Kris Jurka wrote:
>
> > For me this fails with:
> >
> > Bareword "Tie::File" not allowed while "strict subs" in use at
> > /home/jurka/pg/server/postgresql/src/tools/copyright.pl line 28.
> >
>
> This fixes things for me. The copyright matching w
On Fri, Aug 19, 2011 at 05:34:01PM -0400, Kris Jurka wrote:
> On Fri, 19 Aug 2011, Kris Jurka wrote:
>
> > For me this fails with:
> >
> > Bareword "Tie::File" not allowed while "strict subs" in use at
> > /home/jurka/pg/server/postgresql/src/tools/copyright.pl line 28.
>
> This fixes things fo
On Fri, 19 Aug 2011, Kris Jurka wrote:
> For me this fails with:
>
> Bareword "Tie::File" not allowed while "strict subs" in use at
> /home/jurka/pg/server/postgresql/src/tools/copyright.pl line 28.
>
This fixes things for me. The copyright matching wasn't working for me
either without esc
On Fri, Aug 19, 2011 at 6:13 PM, Tom Lane wrote:
> [ getting back to the planner finally ]
>
> Simon Riggs writes:
>> On Wed, Aug 3, 2011 at 8:33 PM, Tom Lane wrote:
>>> Simon Riggs writes:
I think its possible to tell automatically whether we need to replan
always or not based upon t
> Hello. How can we define a global variable in postgresql?
you can also use global structure in plpython for example:
http://www.postgresql.org/docs/9.0/static/plpython-sharing.html
On 8/19/2011 10:51 AM, Bruce Momjian wrote:
David Fetter wrote:
[Here's a new copyright program.]
Thanks. Applied to HEAD. I never liked putting scripts in git that
only I could run, but I thought if something happened to me, it would be
good to record what I did. The Perl solution is perfe
On Fri, Aug 19, 2011 at 4:02 PM, Robert Haas wrote:
> Hmm, you have a point. If 100 backends simultaneously write to 100
> different pages, and all of those pages are all-visible, then it's
> possible that they could end up fighting over the buffer content lock
> on the visibility map page. But
On Fri, Aug 19, 2011 at 3:31 PM, Tom Lane wrote:
>> As for ROLLBACK, I think it should chuck an error instead of doing
>> this funny
>> emit-a-warning-and-silently-arrange-for-the-transaction-to-be-aborted-later
>> thing.
>
> I'm pretty unexcited about changing the behavior of established
> mains
On Fri, Aug 19, 2011 at 2:51 PM, Gokulakannan Somasundaram
wrote:
> On Sat, Aug 20, 2011 at 2:25 AM, Heikki Linnakangas
> wrote:
>>
>> On 19.08.2011 21:06, Gokulakannan Somasundaram wrote:
>>>
>>> If you are following the same design that Heikki put forward, then there
>>> is
>>> a problem with i
Robert Haas writes:
> I spent some time looking at this afternoon and it appears that the
> root of this problem is that we're a bit schizophrenic about whether a
> multi-query command string constitutes a transaction or not.
Yeah. The current behavior sort of automatically adds a BEGIN and a
CO
On Thu, Aug 18, 2011 at 3:57 AM, Marcin Mańk wrote:
> On Wed, Aug 17, 2011 at 11:30 PM, Tom Lane wrote:
>> =?UTF-8?B?TWFyY2luIE1hxYRr?= writes:
>>> psql -c 'release q; prepare q(int) as select 1'
>>> FATAL: ReleaseSavepoint: unexpected state STARTED
>>
>> Can't get terribly excited about that,
On Sat, Aug 20, 2011 at 2:51 AM, Gokulakannan Somasundaram <
gokul...@gmail.com> wrote:
> On Sat, Aug 20, 2011 at 2:25 AM, Heikki Linnakangas <
> heikki.linnakan...@enterprisedb.com> wrote:
>
>> On 19.08.2011 21:06, Gokulakannan Somasundaram wrote:
>>
>>> If you are following the same design that
On Sat, Aug 20, 2011 at 2:25 AM, Heikki Linnakangas <
heikki.linnakan...@enterprisedb.com> wrote:
> On 19.08.2011 21:06, Gokulakannan Somasundaram wrote:
>
>> If you are following the same design that Heikki put forward, then there
>> is
>> a problem with it in maintaining the bits in page and the
On 19.08.2011 21:06, Gokulakannan Somasundaram wrote:
If you are following the same design that Heikki put forward, then there is
a problem with it in maintaining the bits in page and the bits in visibility
map in sync, which we have already discussed.
Are you referring to this:
http://archive
Hello Hackers,
I've recently noticed a particularly strange behaviour of one of my simple
queries:
SELECT ra,dec FROM sdssdr7.photoobjall WHERE ra BETWEEN 175 and 190 AND
dec BETWEEN 17 And 23 ;
The table is quite large (1.1Tb, 10^9 rows, and has Btree indexes on
"ra","dec" columns).
The p
Currently, we have two types of callbacks that can be registered to get
control when an invalidation message is received: syscache callbacks and
relcache callbacks. It strikes me that we might be better advised to
unify these into a single type of callback that gets a
SharedInvalidationMessage str
>
>> Well, that would certainly be alarming if true, but I don't think it
>> is. As far as I can see, the overhead of making the visibility map
>> crash-safe is just (1) a very small percentage increase in the work
>> being done by VACUUM and (2) a slight possibility of extra work done
>> by a for
>
>
> Well, that would certainly be alarming if true, but I don't think it
> is. As far as I can see, the overhead of making the visibility map
> crash-safe is just (1) a very small percentage increase in the work
> being done by VACUUM and (2) a slight possibility of extra work done
> by a foregr
David Fetter wrote:
> Folks,
>
> I noticed that src/tools/copyright looks like it can only be run on
> Bruce's machine, so this translation to Perl is intended:
>
> 1. To make the script idempotent, which allows its safe use in
> automated tools that might run it many times.
>
> 2. To get the
[ getting back to the planner finally ]
Simon Riggs writes:
> On Wed, Aug 3, 2011 at 8:33 PM, Tom Lane wrote:
>> Simon Riggs writes:
>>> I think its possible to tell automatically whether we need to replan
>>> always or not based upon the path we take through selectivity
>>> functions.
>> I do
> Hello. How can we define a global variable in postgresql?
Do you mean session-private, but persistent across transactions?
Configuration parameters can be abused for this purpose.
--
Florian Weimer
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 t
On Fri, Aug 19, 2011 at 11:40 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Fri, Aug 19, 2011 at 11:26 AM, Tom Lane wrote:
>>> No objection to fixing or backpatching this, but I'm not seeing the
>>> argument for treating this module differently from contrib/xml2.
>
>> Because I screwed it up a
On Fri, Aug 19, 2011 at 11:46 AM, Tom Lane wrote:
> Kohei Kaigai writes:
>>> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
>>> Well, they should get at least a warning from referencing undefined
>>> functions, no?
>
>> Yes. User should notice warning messages due to undefined symbols.
>> I'm not cer
Kohei Kaigai writes:
>> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
>> Well, they should get at least a warning from referencing undefined
>> functions, no?
> Yes. User should notice warning messages due to undefined symbols.
> I'm not certain whether it makes sense to add -Werror here, or not.
H
> -Original Message-
> From: Tom Lane [mailto:t...@sss.pgh.pa.us]
> Sent: 19. August 2011 16:34
> To: Kohei Kaigai
> Cc: Robert Haas; Kohei KaiGai; Yeb Havinga; PgHacker
> Subject: Re: [HACKERS] [v9.1] sepgsql - userspace access vector cache
>
> Kohei Kaigai writes:
> > One point I'm worr
Robert Haas writes:
> On Fri, Aug 19, 2011 at 11:26 AM, Tom Lane wrote:
>> No objection to fixing or backpatching this, but I'm not seeing the
>> argument for treating this module differently from contrib/xml2.
> Because I screwed it up accidentally for sepgsql, and I can't screw it
> up for xml
Kohei Kaigai writes:
> One point I'm worrying about is a case when contrib/sepgsql is compiled
> with older libselinux than minimum requirement. In this case, we may not
> notice the broken module unless user tries to load it actually.
> Is there a good idea to ensure compile failure when we try t
On Fri, Aug 19, 2011 at 11:26 AM, Tom Lane wrote:
> Robert Haas writes:
>> On further review, if the initial configure was done without
>> --with-libxml, xml2 is doomed anyway.
>
> True, but it's still possible to build a shlib that will then not work.
> I just did, after manually supplying the r
> -Original Message-
> From: Robert Haas [mailto:robertmh...@gmail.com]
> Sent: 19. August 2011 15:55
> To: Tom Lane
> Cc: Kohei KaiGai; Kohei Kaigai; Yeb Havinga; PgHacker
> Subject: Re: [HACKERS] [v9.1] sepgsql - userspace access vector cache
>
> On Fri, Aug 19, 2011 at 10:31 AM, Robert
Robert Haas writes:
> On further review, if the initial configure was done without
> --with-libxml, xml2 is doomed anyway.
True, but it's still possible to build a shlib that will then not work.
I just did, after manually supplying the right -I switch:
make PROFILE=-I/usr/include/libxml2
Now ad
On Fri, Aug 19, 2011 at 11:22 AM, Bruce Momjian wrote:
> Robert Haas wrote:
>> > I am happy to have pg_upgrade skip upgrading visibility map files --- it
>> > already has code to conditionally process them because they only exist
>> > in >= 8.4:
>> >
>> > ? ? ? ?/* fsm/vm files added in PG 8.4 */
Robert Haas wrote:
> > I am happy to have pg_upgrade skip upgrading visibility map files --- it
> > already has code to conditionally process them because they only exist
> > in >= 8.4:
> >
> > ? ? ? ?/* fsm/vm files added in PG 8.4 */
> > ? ? ? ?if (GET_MAJOR_VERSION(old_cluster.major_version) >=
On Fri, Aug 19, 2011 at 10:58 AM, EazonGuo wrote:
> Hello. How can we define a global variable in postgresql?
I believe CREATE TABLE is the usual mechanism to do this sort of thing.
--
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger han
Hello. How can we define a global variable in postgresql?
--
Best regards
Eazon
On Fri, Aug 19, 2011 at 10:31 AM, Robert Haas wrote:
> On Fri, Aug 19, 2011 at 10:20 AM, Tom Lane wrote:
>>> Why not just:
>>
>>> SHLIB_LINK = -lselinux
>>
>> I wouldn't have any particular objection to that (although I think it's
>> supposed to be += here).
>
> Oh, right.
>
>> I don't see that a
On Fri, Aug 19, 2011 at 10:20 AM, Tom Lane wrote:
>> Why not just:
>
>> SHLIB_LINK = -lselinux
>
> I wouldn't have any particular objection to that (although I think it's
> supposed to be += here).
Oh, right.
> I don't see that any of the other changes
> Kaigai proposed are helpful, though.
I w
Robert Haas writes:
> On Fri, Aug 19, 2011 at 9:59 AM, Tom Lane wrote:
>> This patch seems unnecessary to me.
> Hmm. I see now that it's parallel, but I find it pretty confusing
> that building sepgsql without specifying --with-selinux results in a
> shared library that seems to compile OK but
On Fri, Aug 19, 2011 at 9:19 AM, Gokulakannan Somasundaram
wrote:
> The fact that the
> proposal is for crash safe visibility map, to become a default package of
> any Postgresql table will definitely have wide ranging implications on OLTP
> performance.
Well, that would certainly be alarming if
On Fri, Aug 19, 2011 at 9:59 AM, Tom Lane wrote:
> Kohei KaiGai writes:
>> 2011/8/18 Robert Haas :
>>> Actually, as I look at this more, I think this build system is
>>> completely mis-designed. Given that you want to build sepgsql,
>>> selinux is not an optional feature. So the stuff in
>>> co
Kohei KaiGai writes:
> 2011/8/18 Robert Haas :
>> Actually, as I look at this more, I think this build system is
>> completely mis-designed. Given that you want to build sepgsql,
>> selinux is not an optional feature. So the stuff in
>> contrib/sepgsql/Makefile that is intended to link against l
I wrote:
> I ran into $SUBJECT whilst doing trial RPM packaging of 9.1.
BTW, the failure seems rather hard to provoke at -j4 ... so it was just
bad luck that my first rpmbuild run fell over. However, in manual
testing, it fails pretty much every time at -j16, on my 4-processor
Fedora box.
> > What issue we may face if you take a backups(includes data dir + wal
files)
> > at standby without LVM snapshot?
>
> The backup might be corrupted in arbitrary ways.
>
And what will happen, if one issues a pg_start_backup() on the master, then
takes a file-backup on slave, and issues pg_stop_b
>
>
>> Note that we already have the visibility map, and the accesses needed to
> update it are already there. Granted, we'll have to change the logic
> slightly to make it crash safe, but I don't expect that to add any
> meaningful overhead - the changes are going to be where the bits are set,
> i
Hello
I am sorry, it's noise
regards
Pavel
2011/8/19 Pavel Stehule :
> Hello
>
> I found a bug in plpgsql parser.
>
>
> create table t(a int, b int);
>
> postgres=# \sf fx
> CREATE OR REPLACE FUNCTION public.fx()
> RETURNS void
> LANGUAGE plpgsql
> AS $function$
> declare r record;
> begin
>
Hello
I found a bug in plpgsql parser.
create table t(a int, b int);
postgres=# \sf fx
CREATE OR REPLACE FUNCTION public.fx()
RETURNS void
LANGUAGE plpgsql
AS $function$
declare r record;
begin
r := (10,20)::t;
if true then
raise notice '% %', r.c, r.b;
end if;
end;
$function$
post
I fixed up the security policy for regression test, and chkselinuxenv script.
The revised security policy allows test domains to execute programs
being installed under home directories.
In addition, the revised chkselinuxenv newly checks necessary commands
to run this script itself, and changed th
2011/8/18 Robert Haas :
> On Thu, Aug 18, 2011 at 1:17 PM, Kohei Kaigai
> wrote:
>>> That's lame. I think we need to patch contrib/sepgsql so that it
>>> fails to build in that case, rather than building and then not
>>> working.
>>>
>> It might be the following fix, but I have no idea to genera
Hello
2011/8/19 EazonGuo :
> Hello, I have a question. In SQL Server, we can use @@rowcount to get the
> efftected row which record last query 's effected row .So I have a
> question:
> In Postgresql, how we can get the effected row? Is there some similar
> functions to complete this?
>
It depen
Hello, I have a question. In SQL Server, we can use @@rowcount to get the
efftected row which record last query 's effected row .So I have a
question:
In Postgresql, how we can get the effected row? Is there some similar
functions to complete this?
--
Best regards
Eazon
63 matches
Mail list logo
