2011/12/30 Tom Lane
> Heikki Linnakangas writes:
> > The Linux kernel does this (arch/powerpc/include/asm/ppc-opcode.h):
>
> Yeah, I was looking at that too.
>
> > We can't copy-paste code from Linux directly, and I'm not sure I like
> > that particular phrasing of the macro, but perhaps we shoul
Merlin Moncure writes:
> On Thu, Dec 29, 2011 at 5:10 PM, Jean-Yves F. Barbier <12u...@gmail.com>
> wrote:
>> CREATE INDEX tst1m_name_lu_ix ON tst1m(unaccent(name));
>> ERROR: functions in index expression must be marked IMMUTABLE
> your problem is the unaccent function. it's defined stable be
Excerpts from Marko Kreen's message of jue dic 29 15:22:49 -0300 2011:
>
> On Thu, Dec 29, 2011 at 03:12:50PM -0300, Alvaro Herrera wrote:
> > Excerpts from Marko Kreen's message of jue dic 29 15:04:49 -0300 2011:
> > > 3) Have a way to format aclitem into something
> > >that can used to crea
On Sat, Dec 3, 2011 at 8:04 AM, Heikki Linnakangas
wrote:
> At the moment, if the situation is ambiguous, the system assumes that you're
> restoring from a backup. What your suggestion amounts to is to reverse tht
> assumption, and assume instead that you're doing crash recovery on a system
> wher
On 12/29/2011 05:06 PM, Tom Lane wrote:
Pavel Stehule writes:
2011/12/29 Tom Lane:
What locale are you using?
LANG=cs_CZ.utf8
Fixed, thanks. (It'd be nice if there were a buildfarm member checking
that locale, since it causes problems on a regular basis.)
I hav
2011/12/30 Ants Aasma :
> On Thu, Dec 29, 2011 at 6:44 PM, Kevin Grittner
> wrote:
>
>> positives. To get this right for a checksum in the page header,
>> double-write would need to be used for all cases where
>> full_page_writes now are used (i.e., the first write of a page after
>> a checkpoin
"chris r." writes:
>> Nothing; that looks like a planner bug to me. Please submit a
>> self-contained test case.
> I ported the entire schema to my test DB server and could not reproduce
> the error there. Note that probably recreating the view solves this
> issue. Given this, how should I proce
On Thu, Dec 29, 2011 at 6:44 PM, Kevin Grittner
wrote:
> positives. To get this right for a checksum in the page header,
> double-write would need to be used for all cases where
> full_page_writes now are used (i.e., the first write of a page after
> a checkpoint), and for all unlogged writes (e.
2011/12/29 Tom Lane :
> Pavel Stehule writes:
>> 2011/12/29 Tom Lane :
>>> What locale are you using?
>
>> LANG=cs_CZ.utf8
>
> Fixed, thanks. (It'd be nice if there were a buildfarm member checking
> that locale, since it causes problems on a regular basis.)
>
Thank you
I hope so we will have a
>> So, you tell me, what's wrong with the old view?
>
> Nothing; that looks like a planner bug to me. Please submit a
> self-contained test case.
I ported the entire schema to my test DB server and could not reproduce
the error there. Note that probably recreating the view solves this
issue. Give
"chris r." writes:
> So, you tell me, what's wrong with the old view?
Nothing; that looks like a planner bug to me. Please submit a
self-contained test case.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Hi all,
When SELECTing from one particular view, I get reproducible SEGFAULTs in
my pg 9.1.2 production database. To test for hardware errors, I ran
memtest, which succeeded. I then asked for help in #postgres and got
advice to create stacktraces, but I couldn't find the problem yet.
Scenario: VI
Heikki Linnakangas writes:
> The Linux kernel does this (arch/powerpc/include/asm/ppc-opcode.h):
Yeah, I was looking at that too.
> We can't copy-paste code from Linux directly, and I'm not sure I like
> that particular phrasing of the macro, but perhaps we should steal the
> idea and only use
Pavel Stehule writes:
> 2011/12/29 Tom Lane :
>> What locale are you using?
> LANG=cs_CZ.utf8
Fixed, thanks. (It'd be nice if there were a buildfarm member checking
that locale, since it causes problems on a regular basis.)
regards, tom lane
--
Sent via pgsql-hackers
We document that a polymorphic C-language function may identify the concrete
data type of each argument using calls to get_fn_expr_argtype(). That relies
on FmgrInfo.fn_expr, which only the executor sets. Calls of internal origin,
by way of {Direct,,Oid}FunctionCall*(), don't cons up an fn_expr,
Is there a secret reason why
ALTER DOMAIN foo DROP CONSTRAINT nonexistent;
doesn't report any error?
If not, I think we should add one and also add the usual IF EXISTS
option.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://ww
On 29.12.2011 04:36, Manabu Ori wrote:
I believe lwarx hint would be no harm for recent PowerPC processors.
What I tested are:
(1) Built postgres on POWER6 + RHEL5, which got lwarx hint
included. Then copy these src tree to POWER5 + RHEL4 and
run "make test", finished successful
Hello
LANG=cs_CZ.utf8
Regards
Pavel
2011/12/29 Tom Lane :
> Pavel Stehule writes:
>> I checked yesterday HEAD and there is problem with create_index test
>
> What locale are you using?
>
> regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgres
Pavel Stehule writes:
> I checked yesterday HEAD and there is problem with create_index test
What locale are you using?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.or
On Thu, Dec 29, 2011 at 03:12:50PM -0300, Alvaro Herrera wrote:
> Excerpts from Marko Kreen's message of jue dic 29 15:04:49 -0300 2011:
> > 3) Have a way to format aclitem into something
> >that can used to create GRANT statement easily. Eg:
> >
> > pg_get_privilege_info(
> >
On Thu, Dec 29, 2011 at 11:08:43AM -0600, Kevin Grittner wrote:
> > Heikki Linnakangas wrote:
> > Simon Riggs wrote:
>
> >> OK, then we are talking at cross purposes. Double write buffers,
> >> in the way you explain them allow us to remove full page writes.
> >> They clearly don't do anything t
Excerpts from Marko Kreen's message of jue dic 29 15:04:49 -0300 2011:
> 3) Have a way to format aclitem into something
>that can used to create GRANT statement easily. Eg:
>
> pg_get_privilege_info(
> IN priv aclitem,
> OUT rolename text,
> OUT privlist text[],
>
Hello,
I tried to generalize a function that creates partitions
for a table and found out it's impossible to do it for grants.
Basically, what I want is a child table that takes it's grants
from parent table. IMHO quite reasonable request. But I don't
see a way to do it in pl/pgsql. (Writing p
> Heikki Linnakangas wrote:
> Simon Riggs wrote:
>> OK, then we are talking at cross purposes. Double write buffers,
>> in the way you explain them allow us to remove full page writes.
>> They clearly don't do anything to check page validity on read.
>> Torn pages are not the only fault we wish
> Heikki Linnakangas wrote:
> On 28.12.2011 01:39, Simon Riggs wrote:
>> On Tue, Dec 27, 2011 at 8:05 PM, Heikki Linnakangas
>> wrote:
>>> On 25.12.2011 15:01, Kevin Grittner wrote:
I don't believe that. Double-writing is a technique to avoid
torn pages, but it requires a checksum
Excerpts from Dimitri Fontaine's message of mié dic 28 15:12:48 -0300 2011:
> Tom Lane writes:
> > I wonder whether it's time to drop that file altogether ... it served a
> > purpose back before we integrated contrib into the SGML docs, but now
> > I'm not quite sure why we should bother with it.
Hello
I checked yesterday HEAD and there is problem with create_index test
Regards
Pavel
regression.diffs
Description: Binary data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Wed, Dec 28, 2011 at 5:45 PM, Heikki Linnakangas
wrote:
> On 28.12.2011 11:22, Simon Riggs wrote:
>>
>> On Wed, Dec 28, 2011 at 7:42 AM, Heikki Linnakangas
>> wrote:
>>
How would you know when to look in the double write buffer?
>>>
>>>
>>>
>>> You scan the double-write buffer, and every
28 matches
Mail list logo
