On Apr 22, 2011, at 3:50 PM, Tom Lane wrote:
> Merlin Moncure writes:
>> On Fri, Apr 22, 2011 at 1:28 PM, Peter Eisentraut wrote:
>>> It would probably be more reasonable and feasible to have a setup where
>>> you can end a transaction in plpgsql but a new one would start right
>>> away.
>
>>
I wrote:
> I just noticed that the collation patch has modified char2wchar and
> wchar2char to accept a collation OID as argument ... but it hasn't done
> anything to make those arguments actually work. Since those functions
> depend on wcstombs and mbstowcs, which respond to LC_CTYPE and nothing
Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian writes:
> > > I thought some more about this and I don't want autovacuum to run on the
> > > old server. This is because pg_dumpall --binary-upgrade --schema-only
> > > grabs the datfrozenxid for all the databases at the start, then connect
Jeff Davis wrote:
> On Fri, 2011-04-22 at 17:34 -0400, Bruce Momjian wrote:
> > Tom Lane wrote:
> > > Bruce Momjian writes:
> > > > I thought some more about this and I don't want autovacuum to run on the
> > > > old server. This is because pg_dumpall --binary-upgrade --schema-only
> > > > grabs
On Fri, 2011-04-22 at 17:34 -0400, Bruce Momjian wrote:
> Tom Lane wrote:
> > Bruce Momjian writes:
> > > I thought some more about this and I don't want autovacuum to run on the
> > > old server. This is because pg_dumpall --binary-upgrade --schema-only
> > > grabs the datfrozenxid for all the d
For background, the issue here is that there are three SSI calls that
get invoked even on non-serializable transactions:
- PredicateLockPageSplit/Combine, during B-tree page splits/combines
- PredicateLockTupleRowVersionLink, from heap_update
These have to update any matching SIREAD locks to m
Merlin Moncure wrote:
> hm, another neat thing about this is that it skirts the
> unfortunate confusion between sql 'begin' and plpgsql 'begin'...
I hadn't thought about that. There is the SQL-standard START
TRANSACTION synonym, so there is a way to deal with it -- but since
BEGIN seems to be
On Fri, Apr 22, 2011 at 3:50 PM, Tom Lane wrote:
> Merlin Moncure writes:
>> On Fri, Apr 22, 2011 at 1:28 PM, Peter Eisentraut wrote:
>>> It would probably be more reasonable and feasible to have a setup where
>>> you can end a transaction in plpgsql but a new one would start right
>>> away.
>
>
Tom Lane wrote:
> Bruce Momjian writes:
> > I thought some more about this and I don't want autovacuum to run on the
> > old server. This is because pg_dumpall --binary-upgrade --schema-only
> > grabs the datfrozenxid for all the databases at the start, then connects
> > to each database to gets
Bruce Momjian wrote:
> > > Well, consider that this also locks out non-super users so I figured it
> > > would be good to run the old and new in the same binary upgrade mode.
> > > Again, we can do just the new cluster for 9.1. I can also control the
> > > behavior based on the catalog version nu
Bruce Momjian writes:
> I thought some more about this and I don't want autovacuum to run on the
> old server. This is because pg_dumpall --binary-upgrade --schema-only
> grabs the datfrozenxid for all the databases at the start, then connects
> to each database to gets the relfrozenxids. I don'
Robert Haas wrote:
> On Apr 21, 2011, at 6:22 PM, Bruce Momjian wrote:
> > Tom Lane wrote:
> >> Bruce Momjian writes:
> >>> Tom Lane wrote:
> Huh? Why would that be? Seems like you've done something in the wrong
> place if that's an issue.
> >>
> >>> Yeah, it is complicated. I don't
On 04/22/2011 09:32 AM, Simon Riggs wrote:
OK, that's good, but ISTM we still have a hole during
RemoveOldXlogFiles() where we don't fsync or open/close the file, just
rename it.
This is also something that many applications rely upon working as hoped
for here, even though it's not technic
Merlin Moncure writes:
> On Fri, Apr 22, 2011 at 1:28 PM, Peter Eisentraut wrote:
>> It would probably be more reasonable and feasible to have a setup where
>> you can end a transaction in plpgsql but a new one would start right
>> away.
> ya, that's an idea.
Yeah, that's a good thought. Then
I just noticed that the collation patch has modified char2wchar and
wchar2char to accept a collation OID as argument ... but it hasn't done
anything to make those arguments actually work. Since those functions
depend on wcstombs and mbstowcs, which respond to LC_CTYPE and nothing
else, this flat o
On Fri, Apr 22, 2011 at 1:28 PM, Peter Eisentraut wrote:
> On fre, 2011-04-22 at 08:37 -0500, Merlin Moncure wrote:
>> It wouldn't bother me in the lest that if in plpgsql procedures if you
>> had to set up and tear down a transaction on every line.
>
> It would probably be more reasonable and fea
On fre, 2011-04-22 at 08:37 -0500, Merlin Moncure wrote:
> It wouldn't bother me in the lest that if in plpgsql procedures if you
> had to set up and tear down a transaction on every line.
It would probably be more reasonable and feasible to have a setup where
you can end a transaction in plpgsql
On 04/22/2011 12:06 PM, Tom Lane wrote:
You could possibly lobotomize plpgsql down to a small number of
datatypes and operators that are known not to ever do anything more
interesting than palloc() and elog(), but IMO the usefulness would be
low and the fragility high. It'd be better to give t
On Fri, Apr 22, 2011 at 11:06 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Apr 22, 2011, at 11:10 AM, Tom Lane wrote:
>>> I'd like a pony, too. Let's be perfectly clear about this: there is no
>>> part of plpgsql that can run outside a transaction today, and probably
>>> no part of the other
Tom,
> >> I'd like a pony, too. Let's be perfectly clear about this: there is
> >> no
> >> part of plpgsql that can run outside a transaction today, and
> >> probably
> >> no part of the other PLs either, and changing that "without major
> >> changes" is wishful thinking of the first order.
I alw
Yves Weißig wrote:
> Ok, but I thought more like an automated test, or a test which
> checks if the interface is correctly implemented.
I'm not aware of any automated tests which would test whether a new
index type is correctly implemented. For starters, how would the
test know when the AM sho
"Deka, Rajib IN MAA SL" wrote:
> Finally I setup two machines for primary and backup using the
> following link.
> http://wiki.postgresql.org/wiki/Streaming_Replication
>
> But after starting the backup I got the following messages and
> postgresql service doesn't start.
> 2011-04-22 14:37:54
Robert Haas writes:
> On Apr 22, 2011, at 11:10 AM, Tom Lane wrote:
>> I'd like a pony, too. Let's be perfectly clear about this: there is no
>> part of plpgsql that can run outside a transaction today, and probably
>> no part of the other PLs either, and changing that "without major
>> changes"
Robert Haas wrote:
> On Apr 22, 2011, at 11:10 AM, Tom Lane wrote:
>> I'd like a pony, too.
No ponies for me; make mine an Arabian stallion.
>> Let's be perfectly clear about this: there is no part of plpgsql
>> that can run outside a transaction today, and probably no part of
>> the other
Leonardo Francalanci wrote:
>>> another question regarding indexes. Sadly I can't find enough
>>> info in the documentation. Which of the functions are needed in
>>> order for a index to work?
>>
>> All of them.
>
>
> Maybe I completely misunderstood the question, but some functions
> are "opt
On Apr 22, 2011, at 11:10 AM, Tom Lane wrote:
> "Kevin Grittner" writes:
>> Merlin Moncure wrote:
>>> wouldn't it be better if the current crop of language handlers
>>> could run procedures without major changes? C functions with SPI?
>>> However it's internally implemented, the more userland m
On Fri, Apr 22, 2011 at 10:10 AM, Tom Lane wrote:
> "Kevin Grittner" writes:
>> Merlin Moncure wrote:
>>> wouldn't it be better if the current crop of language handlers
>>> could run procedures without major changes? C functions with SPI?
>>> However it's internally implemented, the more userla
"Kevin Grittner" writes:
> Merlin Moncure wrote:
>> wouldn't it be better if the current crop of language handlers
>> could run procedures without major changes? C functions with SPI?
>> However it's internally implemented, the more userland mindspace
>> recovered for use of writing procedures t
On Tue, Mar 15, 2011 at 10:22:59PM -0400, Noah Misch wrote:
> On Mon, Mar 14, 2011 at 01:56:22PM +0200, Heikki Linnakangas wrote:
> > On 12.03.2011 12:40, Noah Misch wrote:
> >> The installation that inspired my original report recently upgraded from
> >> 9.0.1
> >> to 9.0.3, and your fix did sign
> > another question regarding indexes. Sadly I can't find enough info in
> > the documentation. Which of the functions are needed in order for a
> > index to work?
>
> All of them.
Maybe I completely misunderstood the question, but some functions
are "optionals", such as amgetbitmap, right?
Merlin Moncure wrote:
> Tom Lane wrote:
>> You can't have arithmetic, comparisons, or much of anything
>> outside a transaction with plpgsql. That model just plain
>> doesn't work for this purpose, I think. You really want a
>> control language that's independent of the SQL engine, and for
>>
On Fri, Apr 22, 2011 at 9:29 AM, Tom Lane wrote:
> Merlin Moncure writes:
>> It wouldn't bother me in the lest that if in plpgsql procedures if you
>> had to set up and tear down a transaction on every line.
>
> It would once you noticed the performance impact ...
I'm aware of the impact. It wo
Christoph Berg writes:
> I'm still seeing that problem: 9.1 HEAD compiled in my $HOME, with
> Debian's 9.0.1-2 libpq5 in /usr/lib:
> $ LC_ALL=C bin/psql
> psql: connection pointer is NULL
> Upgrading to libpq5 9.0.4-1 makes things a bit better:
> $ LC_ALL=C bin/psql
> psql: invalid connection opt
On Thu, Apr 21, 2011 at 4:55 PM, Tom Lane wrote:
> The traditional standard is that the filesystem is supposed to take
> care of its own metadata, and even Linux filesystems have pretty much
> figured that out. I don't really see a need for us to be nursemaiding
> the filesystem. At most there's
Merlin Moncure writes:
> It wouldn't bother me in the lest that if in plpgsql procedures if you
> had to set up and tear down a transaction on every line.
It would once you noticed the performance impact ...
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsq
=?ISO-8859-15?Q?Yves_Wei=DFig?= writes:
> another question regarding indexes. Sadly I can't find enough info in
> the documentation. Which of the functions are needed in order for a
> index to work?
All of them.
regards, tom lane
--
Sent via pgsql-hackers mailing list (
On Thu, Apr 21, 2011 at 5:07 PM, Tom Lane wrote:
> Merlin Moncure writes:
>> On Thu, Apr 21, 2011 at 1:13 PM, Tom Lane wrote:
>>> 3. What sort of primitive operations do you expect the SP to be
>>> able to execute "outside a transaction"? The plpgsql model where
>>> all the primitive operations
On Fri, Apr 22, 2011 at 1:35 PM, Greg Smith wrote:
> Simon Riggs wrote:
>>
>> We do issue fsync and then close, but only when we switch log files.
>> We don't do that as part of the normal commit path.
>>
>
> Since all these files are zero-filled before use, the space is allocated for
> them, and
Hi,
another question regarding indexes. Sadly I can't find enough info in
the documentation. Which of the functions are needed in order for a
index to work? I am developing a prototype so it would be great if not
all of the functions have to be implemented. E.g. are amcostestimate or
amoptions nee
On Thu, Apr 21, 2011 at 8:34 PM, Robert Haas wrote:
> On Apr 21, 2011, at 3:51 PM, Merlin Moncure wrote:
>> If you do it that (base it on AT) way, then you can't:
>> 1) call any utility command (vacuum, etc)
>> 2) run for an arbitrary amount of time
>> 3) discard any locks (except advisory)
>> 4)
Simon Riggs wrote:
We do issue fsync and then close, but only when we switch log files.
We don't do that as part of the normal commit path.
Since all these files are zero-filled before use, the space is allocated
for them, and the remaining important filesystem layout metadata gets
flushed
On Fri, Apr 22, 2011 at 4:51 AM, Greg Smith wrote:
> On 04/21/2011 04:26 AM, Simon Riggs wrote:
>>
>> However, that begs the question of what happens with WAL. At present,
>> we do nothing to ensure that "the entry in the directory containing
>> the file has also reached disk".
>>
>
>
> Well, we d
Re: Tom Lane 2011-04-03 <1397.1301782...@sss.pgh.pa.us>
> Yeah, that's clearly a bug --- fix committed, thanks for the patch!
>
> It could explain Devrim's report if the parameters passed by psql had
> some problem that was detectable by conninfo_array_parse(). That seems
> a bit unlikely, but I
Finally I setup two machines for primary and backup using the following link.
http://wiki.postgresql.org/wiki/Streaming_Replication
But after starting the backup I got the following messages and postgresql
service doesn't start.
2011-04-22 14:37:54 ETC/GMT LOG: database system was shut down in
> Maybe you should change xl_act_commit to have a separate list of rels to
> drop the init fork for (instead of mixing those with the list of files to
> drop as a whole).
I tried to follow your suggestion, thank you very much.
Here's a first attempt at the patch.
I "tested" it with:
crea
Ok, but I thought more like an automated test, or a test which checks if
the interface is correctly implemented. By the way, tho broaden the
topic, what would be the best way to debug in pg? elog? asserts?
Am 22.04.2011 01:26, schrieb Josh Berkus:
> On 4/21/11 1:28 PM, Kevin Grittner wrote:
>> Tha
Andrew Dunstan wrote:
Personally, I want pgindent installed in /usr/local/ or similar. That
way I can have multiple trees and it will work in all of them without
my having to build it for each. What I don't want is for the installed
patched BSD indent to conflict with the system's indent, which
Thanks a lot.
I got the idea now.
Rajib Deka
SIEMENS Ltd.
Robert V Chandran Tower, First Floor, West Wing,
#149, Velechery Tambaram Main Road, Pallikaranai, Chennai-100, INDIA.
www.siemens.com
Mob: +91-9176780669 | E-Mail: rajib.d...@siemens.com
-Original Message-
From: Cédric Villemain
Hello
>
> This isn't very well known because the whole MySQL community fracturing has
> impacted their ability to actually release this overhaul--seems like they
> spend all their time just trying to add support for each new engine of the
> month. I don't even like Lua, yet this still seems like
49 matches
Mail list logo
