On Fri, Feb 18, 2011 at 20:12, Itagaki Takahiro
wrote:
> + extern char *pg_any_to_server(const char *s, int len, int encoding);
> + extern char *pg_server_to_any(const char *s, int len, int encoding);
I applied the version with additional codes for file_fdw.
--
Itagaki Takahiro
--
Sent via pg
Tom Lane wrote:
> Bruce Momjian writes:
> > Tom Lane wrote:
> >> You seem to be confusing one limitation in one code path with the
> >> overall meaning of maintenance_work_mem.
>
> > Oh, OK, so sorts are limited, but not hash sizes? Are there any other
> > uses? Should this be documented someho
On Sun, Feb 20, 2011 at 11:20:22AM +0100, Radosław Smogura wrote:
> Just patch for missing procedures for void send/recv
>
> Regards,
> Radek
Thanks! :)
Style note: the project doesn't use // as a comment-to-end-of-line in
C because some supported compilers don't understand it.
Cheers,
David.
-
Tom Lane wrote:
> Bruce Momjian writes:
> > Bruce Momjian wrote:
> >> Can someone update the PostgreSQL shared memory usage table for 9.0?
> >>
> >> http://www.postgresql.org/docs/9.0/static/kernel-resources.html#SYSVIPC
> >>
> >> Right now it says "Approximate shared memory bytes required (as o
I found "make installcheck" for contrib/unaccent in master is failed
on my machine, The regressions.diffs attached.
I'm not sure the reason because BuildFarm machines are all OK,
but we might need some checks in addition to database encoding.
* OS:
Linux 2.6.35.10-74.fc14.x86_64 #1 SMP Thu Dec 23
"Kevin Grittner" wrote:
> I'm proceeding on this basis.
Result attached. I found myself passing around the tuple xmin value
just about everywhere that the predicate lock target tag was being
passed, so it finally dawned on me that this logically belonged as
part of the target tag. That simplifi
On Feb21, 2011, at 00:09 , Jaime Casanova wrote:
> On Sun, Feb 20, 2011 at 7:20 AM, Florian Pflug wrote:
>> On Feb20, 2011, at 08:12 , Jaime Casanova wrote:
>>> considering that synchronous_replication to on means that we *want*
>>> durability, and that synchronous_commit to off means we don't *ca
Tom Lane wrote:
> Bruce Momjian writes:
> > Well, I figure it will be hard to allow larger maximums, but can we make
> > the GUC variable maximums be more realistic? Right now it is
> > MAX_KILOBYTES (INT_MAX).
>
> You seem to be confusing one limitation in one code path with the
> overall meani
On Sun, Feb 20, 2011 at 7:20 AM, Florian Pflug wrote:
> On Feb20, 2011, at 08:12 , Jaime Casanova wrote:
>> considering that synchronous_replication to on means that we *want*
>> durability, and that synchronous_commit to off means we don't *care*
>> about durability. Then the real question here i
I wrote:
> Robert Haas writes:
>> On Fri, Feb 18, 2011 at 10:47 AM, Tom Lane wrote:
>>> The main downside of that is that relation relkinds would have
>>> to become fixed (because there would be no practical way of updating
>>> RTEs in stored rules), which means the "convert relation to view" hac
Bruce Momjian writes:
> Tom Lane wrote:
>> You seem to be confusing one limitation in one code path with the
>> overall meaning of maintenance_work_mem.
> Oh, OK, so sorts are limited, but not hash sizes? Are there any other
> uses? Should this be documented somehow? What is the actual sort
>
Hi,
Magnus Hagander writes:
> Better late than never (or?), here's the final cleanup of
> pg_streamrecv for moving into the main distribution, per discussion
> back in late dec or early jan. It also includes the "stream logs in
> parallel to backup" part that was not completed on pg_basebackup.
Alexander Korotkov writes:
> Hacker,
> I found two issues in fuzzystrmatch contrib.
> 1) Incorrect s_data shift in levenshtein calculation with threshold with
> multibyte characters. "i" index was used instead of "start_column".
> 2) Missing dependency of fuzzystrmatch.o on levenshtein.c
> Patch
Shigeru HANADA writes:
> [ 20110218-file_fdw.patch ]
I've adjusted this to fit the extensions infrastructure and the
committed version of the FDW API patch, and applied it.
>> * You might forget some combination or unspecified options in
>> file_fdw_validator().
>> For example, format == NULL or
Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= writes:
> On Sun, 2011-02-20 at 12:45 -0500, Tom Lane wrote:
>> No, I can't. I get something like this on stderr:
>>
>> LOG: invalid connection type "zlocal"
> Err, please try putting an extra char before the first comment line,
> like:
> w# PostgreSQL Clie
2011/2/20 Devrim GÜNDÜZ :
> On Sun, 2011-02-20 at 12:45 -0500, Tom Lane wrote:
>>
>> > None of them logged anything to anywhere. You can reproduce it on
>> your
>> > machine, too.
>>
>> No, I can't. I get something like this on stderr:
>>
>> LOG: invalid connection type "zlocal"
>
> Err, please t
On Sun, 2011-02-20 at 12:45 -0500, Tom Lane wrote:
>
> > None of them logged anything to anywhere. You can reproduce it on
> your
> > machine, too.
>
> No, I can't. I get something like this on stderr:
>
> LOG: invalid connection type "zlocal"
Err, please try putting an extra char before the
Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= writes:
> On Sun, 2011-02-20 at 10:39 -0500, Tom Lane wrote:
>> That information would certainly be logged somewhere. Maybe you
>> looked in the wrong log file? Or you're using one of those
>> configurations where early output to stderr goes to /dev/null?
> N
On Sun, 2011-02-20 at 10:39 -0500, Tom Lane wrote:
>
> > Is it possible to drop something to (startup) log file and mention
> > about the syntax error in hba file?
>
> That information would certainly be logged somewhere. Maybe you
> looked in the wrong log file? Or you're using one of those
>
On Fri, Feb 18, 2011 at 6:59 PM, Andrew Dunstan wrote:
> The server is running as a warm standby, and the client's application tries
> to connect to both the master and the slave, accepting whichever lets it
> connect (hence hot standby is not turned on).
>...
> #2 0x005de645 in LockBuf
Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= writes:
> Yesterday I spent about half an hour to dig an issue on my laptop -- 9.0
> instance did not start, and there were nothing in the logs. Eventually I
> straced postmaster on start, and noticed an extra char in the
> pg_hba.conf, which caused postmaster no
Bruce Momjian writes:
> Bruce Momjian wrote:
>> Can someone update the PostgreSQL shared memory usage table for 9.0?
>>
>> http://www.postgresql.org/docs/9.0/static/kernel-resources.html#SYSVIPC
>>
>> Right now it says "Approximate shared memory bytes required (as of
>> 8.3)".
> This documentat
Bruce Momjian writes:
> Well, I figure it will be hard to allow larger maximums, but can we make
> the GUC variable maximums be more realistic? Right now it is
> MAX_KILOBYTES (INT_MAX).
You seem to be confusing one limitation in one code path with the
overall meaning of maintenance_work_mem.
--On 20. Februar 2011 15:48:06 +0100 Bernd Helmle
wrote:
Well, I figure it will be hard to allow larger maximums, but can we make
the GUC variable maximums be more realistic? Right now it is
MAX_KILOBYTES (INT_MAX).
This is something i proposed some time ago, too. At least, it will stop
--On 20. Februar 2011 09:32:02 -0500 Bruce Momjian wrote:
Well, I figure it will be hard to allow larger maximums, but can we make
the GUC variable maximums be more realistic? Right now it is
MAX_KILOBYTES (INT_MAX).
This is something i proposed some time ago, too. At least, it will stop u
Josh Berkus wrote:
>
> > Is this a TODO? Can we easily fix the tuplesort.c code?
>
> Easily, no. But that's not a reason for it to not be a TODO.
>
> I, too, would like to be able to make use of 32GB of work_mem effectively.
[ repost to the right thread.]
Well, I figure it will be hard to al
Devrim G?ND?Z wrote:
> On Wed, 2011-02-16 at 23:24 +0200, Peter Eisentraut wrote:
> >
> > > But before expending time on that, I'd want to see some evidence
> > that
> > > it's actually helpful for production situations. I'm a bit dubious
> > > that you're going to gain much here.
> >
> > If you
Bruce Momjian wrote:
> This documentation
This page was missed in the SSI documentation update. I don't want
to get distracted by it today, but we'll need to get this done for
9.1. I guess I need to grep the sgml files for other mentions of
max_locks_per_transaction for other possible misses
On Feb20, 2011, at 08:12 , Jaime Casanova wrote:
> considering that synchronous_replication to on means that we *want*
> durability, and that synchronous_commit to off means we don't *care*
> about durability. Then the real question here is: in the presence of
> synchronous_replication to on (which
Yesterday I spent about half an hour to dig an issue on my laptop -- 9.0
instance did not start, and there were nothing in the logs. Eventually I
straced postmaster on start, and noticed an extra char in the
pg_hba.conf, which caused postmaster not to start.
Is it possible to drop something to (s
On Wed, 2011-02-16 at 23:24 +0200, Peter Eisentraut wrote:
>
> > But before expending time on that, I'd want to see some evidence
> that
> > it's actually helpful for production situations. I'm a bit dubious
> > that you're going to gain much here.
>
> If you want to build an index on a 500GB ta
Just patch for missing procedures for void send/recv
Regards,
Radek
diff --git a/src/backend/utils/adt/pseudotypes.c b/src/backend/utils/adt/pseudotypes.c
index d9329f8..614eb98 100644
--- a/src/backend/utils/adt/pseudotypes.c
+++ b/src/backend/utils/adt/pseudotypes.c
@@ -212,7 +212,20 @@ void_out
On 20.02.2011 08:03, wrote:
Hello, I had defined user-defined function and type in database A by using user
Root.when i want to access the function and type in another database B by using
the same user Root, but found that i could't access them. How to make the
user-defined function o
Hello, I had defined user-defined function and type in database A by using user
Root.when i want to access the function and type in another database B by using
the same user Root, but found that i could't access them. How to make the
user-defined function or type being accessed in the global dat
34 matches
Mail list logo
