> From: Jose Ildefonso Camargo Tolosa [ildefonso.cama...@gmail.com]
> Sent: Saturday, July 14, 2012 9:36 AM
>On Fri, Jul 13, 2012 at 11:12 PM, Amit kapila wrote:
> From: pgsql-hackers-ow...@postgresql.org [pgsql-hackers-ow...@postgresql.org]
> on behalf of Jose Ildefonso Camargo Tolosa [ildefonso
On Fri, Jul 13, 2012 at 11:12 PM, Amit kapila wrote:
> From: pgsql-hackers-ow...@postgresql.org [pgsql-hackers-ow...@postgresql.org]
> on behalf of Jose Ildefonso Camargo Tolosa [ildefonso.cama...@gmail.com]
> Sent: Saturday, July 14, 2012 6:08 AM
> On Fri, Jul 13, 2012 at 10:22 AM, Bruce Momjian
From: pgsql-hackers-ow...@postgresql.org [pgsql-hackers-ow...@postgresql.org]
on behalf of Jose Ildefonso Camargo Tolosa [ildefonso.cama...@gmail.com]
Sent: Saturday, July 14, 2012 6:08 AM
On Fri, Jul 13, 2012 at 10:22 AM, Bruce Momjian wrote:
> On Fri, Jul 13, 2012 at 09:12:56AM +0200, Hampus We
On Fri, Jul 13, 2012 at 10:22 AM, Bruce Momjian wrote:
> On Fri, Jul 13, 2012 at 09:12:56AM +0200, Hampus Wessman wrote:
>> How you decide what to do with the servers on failures isn't that
>> important here, really. You can probably run e.g. Pacemaker on 3+
>> machines and have it check for quoru
Hi Hampus,
On Fri, Jul 13, 2012 at 2:42 AM, Hampus Wessman wrote:
> Hi all,
>
> Here are some (slightly too long) thoughts about this.
Nah, not that long.
>
> Shaun Thomas skrev 2012-07-12 22:40:
>
>> On 07/12/2012 12:02 PM, Bruce Momjian wrote:
>>
>>> Well, the problem also exists if add it as
Jeff Davis writes:
> One point about the commit message: fadvise does not block to go into
> the request queue, sync_file_range does. The problem with fadvise is
> that, when the request queue is small, it fills up so fast that most of
> the requests never make it in, and fadvise is essentially a
On Fri, Jul 13, 2012 at 12:25 AM, Amit Kapila wrote:
>
>> From: pgsql-hackers-ow...@postgresql.org
> [mailto:pgsql-hackers-ow...@postgresql.org]
>> On Behalf Of Jose Ildefonso Camargo Tolosa
>>>On Thu, Jul 12, 2012 at 9:28 AM, Aidan Van Dyk wrote:
>> On Thu, Jul 12, 2012 at 9:21 AM, Shaun Thomas
On Fri, 2012-07-13 at 17:35 -0400, Tom Lane wrote:
> I wrote:
> > I'm picking up this patch now. What I'm inclined to do about the -N
> > business is to commit without that, so that we get a round of testing
> > in the buildfarm and find out about any portability issues, but then
> > change to use
Alvaro Herrera writes:
> For what it's worth, I would appreciate it if you would post the lock
> timeout patch for the upcoming commitfest.
+1. I think it's reasonable to get the infrastructure patch in now,
but we are running out of time in this commitfest (and there's still
a lot of patches th
Excerpts from Andrew Dunstan's message of vie jul 13 16:05:37 -0400 2012:
> Why does the isolation check take such a long time? On some of my slower
> buildfarm members I am thinking of disabling it because it takes so
> long. This single test typically takes longer than a full serial
> standar
Boszormenyi Zoltan writes:
>>> Try SET deadlock_timeout = 0;
Actually, when I try that I get
ERROR: 0 is outside the valid range for parameter "deadlock_timeout" (1 ..
2147483647)
So I don't see any bug here. The places that are unconditionally doing
"enable_timeout_after(..., DeadlockTimeou
Excerpts from Boszormenyi Zoltan's message of vie jul 13 18:11:27 -0400 2012:
> Regarding the lock_timeout functionality: the patch can be reduced to
> about half of its current size and it would be a lot less intrusive if the
> LockAcquire() callers don't need to report the individual object typ
2012-07-13 23:51 keltezéssel, Tom Lane írta:
Boszormenyi Zoltan writes:
While doing it, I discovered another bug you introduced.
enable_timeout_after(..., 0); would set an alarm instead of ignoring it.
Try SET deadlock_timeout = 0;
Hm. I don't think it's a bug for enable_timeout_after(..., 0)
Jeff Davis writes:
> For the case of initdb, the data needing to be fsync'd is effectively
> constant, and it's a lot of small files. If the requests don't make it
> to the io scheduler queue before fsync, the kernel doesn't have an
> opportunity to schedule them properly.
> But for larger amount
Boszormenyi Zoltan writes:
> While doing it, I discovered another bug you introduced.
> enable_timeout_after(..., 0); would set an alarm instead of ignoring it.
> Try SET deadlock_timeout = 0;
Hm. I don't think it's a bug for enable_timeout_after(..., 0) to cause
a timeout ... but we'll have to
Boszormenyi Zoltan writes:
> It means that StatementTimeout losts its precision. It would trigger
> in the future counting from "now" instead of counting from
> GetCurrentStatementStartTimestamp().
That is, in fact, better not worse. Note the comment in the existing
code:
* Begin state
On Fri, 2012-07-13 at 15:21 -0400, Tom Lane wrote:
> No, that's incorrect: the fadvise is there, inside pg_flush_data() which
> is done during the writing phase.
Yeah, Andres pointed that out, also.
> It seems to me that if we think
> sync_file_range is a win, we ought to be using it in pg_flus
2012-07-13 22:32 keltezéssel, Boszormenyi Zoltan írta:
2012-07-12 19:05 keltezéssel, Tom Lane írta:
I haven't really looked at the second patch yet, but at minimum that
will need some rebasing to match the API tweaks here.
Yes, I will do that.
While doing it, I discovered another bug you in
I wrote:
> I'm picking up this patch now. What I'm inclined to do about the -N
> business is to commit without that, so that we get a round of testing
> in the buildfarm and find out about any portability issues, but then
> change to use -N after a week or so. I agree that in the long run
> we do
2012-07-12 19:05 keltezéssel, Tom Lane írta:
Here is a revised version of the timeout-infrastructure patch.
I whacked it around quite a bit, notably:
* I decided that the most convenient way to handle the initialization
issue was to combine establishment of the signal handler with resetting
of t
Why does the isolation check take such a long time? On some of my slower
buildfarm members I am thinking of disabling it because it takes so
long. This single test typically takes longer than a full serial
standard regression test. Is there any way we could make it faster?
cheers
andrew
--
Bruce Momjian writes:
> On Fri, Jul 13, 2012 at 10:34:35PM +0300, Peter Eisentraut wrote:
>> I would rather get rid of this %X/%X notation.
> +1
I'm for it if we can find a less messy way of dealing with the
platform-specific-format-code issue. I don't want to be plugging
UINT64_FORMAT into str
On Fri, Jul 13, 2012 at 10:34:35PM +0300, Peter Eisentraut wrote:
> On tor, 2012-07-12 at 10:13 +0300, Heikki Linnakangas wrote:
> > One idea would be to use a macro, like this:
> >
> > #define XLOGRECPTR_FMT_ARGS(recptr) (uint32) ((recptr) >> 32),
> > (uint32)
> > (recptr)
> >
> > elog(LOG, "cu
On tor, 2012-07-12 at 19:44 +0900, Shigeru HANADA wrote:
> Yes, I've proposed to rename existing postgresql_fdw_validator to
> dblink_fdw_validator and move it into contrib/dblink so that pgsql_fdw
> can use the name "postgresql_fdw" and "postgresql_fdw_validator".
I was somehow under the impressi
On tor, 2012-07-12 at 16:14 +0200, Joel Jacobson wrote:
> Could work. But I think it's more relevant and useful to keep all objects
> in a schema in its own directory.
Personally, I hate this proposed nested directory structure. I would
like to have all objects in one directory.
But there is a l
On ons, 2012-07-11 at 17:20 -0400, Alvaro Herrera wrote:
> operator_!___numeric.sql (postfix, name does not need escape)
> operator_%7C%2F_integer__.sql (prefix)
> operator_%3C_bit_varying__bit_varying.sql (type name with spaces,
> changed to _)
I'm not sure if it makes things better to escape som
On tor, 2012-07-12 at 10:13 +0300, Heikki Linnakangas wrote:
> One idea would be to use a macro, like this:
>
> #define XLOGRECPTR_FMT_ARGS(recptr) (uint32) ((recptr) >> 32),
> (uint32)
> (recptr)
>
> elog(LOG, "current WAL location is %X/%X",
> XLOGRECPTR_FMT_ARGS(RecPtr));
>
I would rather ge
Jeff Davis writes:
> On Mon, 2012-06-18 at 20:57 +0200, Andres Freund wrote:
>> Ok. Sensible reasons. I dislike that we know have two files using different
>> logic (copydir.c only using fadvise, initdb using sync_file_range if
>> available). Maybe we should just move the fadvise and sync_file_r
Andres Freund writes:
> On Tuesday, June 19, 2012 07:22:02 PM Jeff Davis wrote:
>> Right now I'm inclined to leave the patch as-is.
> Fine with that, I wanted to bring it up and see it documented.
> I have marked it with ready for committer. That committer needs to decide on -
> N in the regress
Excerpts from Kyotaro HORIGUCHI's message of jue jul 12 00:09:19 -0400 2012:
>
> Hmm... Sorry for immature patch..
No need to apologize.
> > ... and this story hasn't ended yet, because one of the new tests is
> > failing. See here:
> >
> > http://buildfarm.postgresql.org/cgi-bin/show_log.pl?
Michael Schneider writes:
> whenever pg calls my input function, the type modifier parameter is
> ALWAYS (-1).
> ...
> How can I convince pg to call the input function with the correct type
> modifier?
You can't. Per the comment in coerce_type:
* For most types we pass typmod -1 to t
Hi,
whenever pg calls my input function, the type modifier parameter is
ALWAYS (-1). If I specify a type modifier like
SELECT 'Hello World!'::my_string_type(MODIFIER1,MODIFIER2);
then pg:
1. calls the my_string_type-typmod_in function, and gets the correct result
2. calls the my_string_type-i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
Thanks to the indications given by Tom Lane, I was able to make use of
parameterized path in our multicorn extension.
For example, given a (local) table "real_table" and another (foreign)
table "foreign_table", having the same set of columns,
Markus Wanner writes:
> On 07/13/2012 11:33 AM, Markus Wanner wrote:
>> As another minor improvement, it doesn't seem necessary to repeatedly
>> set the rootBlkno.
> Sorry, my mail program delivered an older version of the patch, which
> didn't reflect that change. Here's what I intended to send.
On 10 July 2012 18:24, David Fetter wrote:
> On Tue, Jul 10, 2012 at 12:00:06PM -0400, Tom Lane wrote:
> > Josh Kupershmidt writes:
> > > On Tue, Jul 10, 2012 at 2:09 AM, Colin 't Hart
> wrote:
> > >> Attached please find a trivial patch for psql which adds a \n
> > >> meta command as a shortcu
On 10 July 2012 18:00, Tom Lane wrote:
> Josh Kupershmidt writes:
> > On Tue, Jul 10, 2012 at 2:09 AM, Colin 't Hart
> wrote:
> >> Attached please find a trivial patch for psql which adds a \n meta
> command
> >> as a shortcut for typing set search_path =.
>
> > I think the use-case is a bit na
On Fri, Jul 13, 2012 at 09:12:56AM +0200, Hampus Wessman wrote:
> How you decide what to do with the servers on failures isn't that
> important here, really. You can probably run e.g. Pacemaker on 3+
> machines and have it check for quorums to accomplish this. That's a
> good approach at least. You
2012-07-11 22:59 keltezéssel, Tom Lane írta:
I wrote:
I'm starting to look at this patch now.
After reading this further, I think that the "sched_next" option is a
bad idea and we should get rid of it. AFAICT, what it is meant to do
is (if !sched_next) automatically do "disable_all_timeouts(tr
On Fri, Jul 13, 2012 at 7:03 PM, Andrew Dunstan wrote:
>
> On 07/13/2012 09:12 AM, Atri Sharma wrote:
>>
>> On Fri, Jul 13, 2012 at 6:40 PM, Andrew Dunstan
>> wrote:
>>>
>>> On 07/13/2012 08:57 AM, Atri Sharma wrote:
On Fri, Jul 13, 2012 at 6:13 PM, Andrew Dunstan
wrote:
>
>>>
On 07/13/2012 09:12 AM, Atri Sharma wrote:
On Fri, Jul 13, 2012 at 6:40 PM, Andrew Dunstan wrote:
On 07/13/2012 08:57 AM, Atri Sharma wrote:
On Fri, Jul 13, 2012 at 6:13 PM, Andrew Dunstan
wrote:
On 07/13/2012 08:07 AM, Albe Laurenz wrote:
I have read a report that extensions built with Mi
2012-07-11 21:47 keltezéssel, Tom Lane írta:
Boszormenyi Zoltan writes:
Attached are the refreshed patches. InitializeTimeouts() can be called
twice and PGSemaphoreTimedLock() returns bool now. This saves
two calls to get_timeout_indicator().
I'm starting to look at this patch now. There are
On Fri, Jul 13, 2012 at 6:40 PM, Andrew Dunstan wrote:
>
> On 07/13/2012 08:57 AM, Atri Sharma wrote:
>>
>> On Fri, Jul 13, 2012 at 6:13 PM, Andrew Dunstan
>> wrote:
>>>
>>> On 07/13/2012 08:07 AM, Albe Laurenz wrote:
I have read a report that extensions built with MinGW are compatible
On 07/13/2012 08:57 AM, Atri Sharma wrote:
On Fri, Jul 13, 2012 at 6:13 PM, Andrew Dunstan wrote:
On 07/13/2012 08:07 AM, Albe Laurenz wrote:
I have read a report that extensions built with MinGW are compatible with
EDB's binaries if you use --disable-float8-byval
(http://www.postgresonline.c
On Fri, Jul 13, 2012 at 6:13 PM, Andrew Dunstan wrote:
>
> On 07/13/2012 08:07 AM, Albe Laurenz wrote:
>>
>> I have read a report that extensions built with MinGW are compatible with
>> EDB's binaries if you use --disable-float8-byval
>> (http://www.postgresonline.com/journal/archives/246-ODBC-For
On 07/13/2012 08:07 AM, Albe Laurenz wrote:
I have read a report that extensions built with MinGW are compatible
with EDB's binaries if you use --disable-float8-byval
(http://www.postgresonline.com/journal/archives/246-ODBC-Foreign-Data-wr
apper-odbc_fdw-on-windows.html).
Unfortunately, not
Atri Sharma wrote:
> How do I use PGXS with MinGW)?
Just as described in
http://www.postgresql.org/docs/9.1/static/extend-pgxs.html
Build PostgreSQL with MinGW
(./configure && make && make install)
and use a Makefile as shown in the documentation.
Yours,
Laurenz Albe
--
Sent via pgsql-hackers
On Fri, Jul 13, 2012 at 5:37 PM, Albe Laurenz wrote:
> Atri Sharma wrote:
>> On Fri, Jul 13, 2012 at 2:11 PM, Dave Page wrote:
>>> On Fri, Jul 13, 2012 at 9:31 AM, Atri Sharma
> wrote:
I am trying to install my FDW project on windows.I did some research
and I believe I shall be requiri
Atri Sharma wrote:
> On Fri, Jul 13, 2012 at 2:11 PM, Dave Page wrote:
>> On Fri, Jul 13, 2012 at 9:31 AM, Atri Sharma
wrote:
>>> I am trying to install my FDW project on windows.I did some research
>>> and I believe I shall be requiring pre compiled binaries(dll
files).I
>>> tried cross compilin
On 07/13/2012 11:33 AM, Markus Wanner wrote:
> As another minor improvement, it doesn't seem necessary to repeatedly
> set the rootBlkno.
Sorry, my mail program delivered an older version of the patch, which
didn't reflect that change. Here's what I intended to send.
Regards
Markus Wanner
#
# Mi
On 12/07/12 11:08, Heikki Linnakangas wrote:
On 07.07.2012 00:12, Jan Urbański wrote:
On 06/07/12 22:47, Peter Eisentraut wrote:
On fre, 2012-07-06 at 18:53 +0300, Heikki Linnakangas wrote:
What shall we do about those? Ignore them? Document that if you're
sing
one of these encodings then PL/P
On Mon, Jul 09, 2012 at 05:35:15PM +0900, Shigeru HANADA wrote:
> Hi Ryan,
>
> On Mon, Jun 25, 2012 at 9:00 PM, Ryan Kelly wrote:
> >> Connection attempt by \connect command could be also canceled by
> >> pressing Ctrl+C on psql prompt.
> >>
> >> In addition, I tried setting PGCONNECT_TIMEOUT to
On Mon, Jun 25, 2012 at 2:26 PM, Magnus Hagander wrote:
> On Mon, Jun 25, 2012 at 4:04 AM, Robert Haas wrote:
>> On Fri, Jun 22, 2012 at 12:38 PM, Euler Taveira wrote:
>>> On 20-06-2012 17:40, Marko Kreen wrote:
On Wed, Jun 20, 2012 at 10:05 PM, Florian Pflug wrote:
> I'm starting to t
On Fri, Jul 13, 2012 at 3:35 PM, Dave Page wrote:
> On Fri, Jul 13, 2012 at 11:03 AM, Atri Sharma wrote:
>>
>> Okies,thanks.
>>
>> Another thing,could you please help me in installation of my FDW
>> project in packaged installations of PostgreSQL in Debian and Red
>> hat?I did source based instal
On Fri, Jul 13, 2012 at 11:03 AM, Atri Sharma wrote:
>
> Okies,thanks.
>
> Another thing,could you please help me in installation of my FDW
> project in packaged installations of PostgreSQL in Debian and Red
> hat?I did source based installations.
I'm not really involved with the native packages
On Fri, Jul 13, 2012 at 3:21 PM, Dave Page wrote:
> On Fri, Jul 13, 2012 at 10:04 AM, Atri Sharma wrote:
>>
>> Thanks for the advice.i shall build PostgreSQL from sources in
>> windows,then,try to get vc++ installed and configured"?
>
> No, the other way round - that'll prove VC++ is setup corre
On Fri, Jul 13, 2012 at 10:04 AM, Atri Sharma wrote:
>
> Thanks for the advice.i shall build PostgreSQL from sources in
> windows,then,try to get vc++ installed and configured"?
No, the other way round - that'll prove VC++ is setup correctly.
Note that you don't actually need to build PG from s
On 07/11/2012 05:45 AM, Tom Lane wrote:
> I'm also inclined to think that the "while (stack)" coding of the rest
> of it is wrong, misleading, or both, on precisely the same grounds: if
> that loop ever did fall out at the test, the function would have failed
> to honor its contract. The only corr
Sent from my iPad
On 13-Jul-2012, at 2:23 PM, Dave Page wrote:
> On Fri, Jul 13, 2012 at 9:46 AM, Atri Sharma wrote:
>>
>> Hi Dave,
>>
>> I am sorry,I am not too sure about EDB.Cannot I cross compile even for
>> EnterpriseDB version?
>
> I doubt it. The EDB builds are compiled with VC++ 20
On Fri, Jul 13, 2012 at 9:46 AM, Atri Sharma wrote:
>
> Hi Dave,
>
> I am sorry,I am not too sure about EDB.Cannot I cross compile even for
> EnterpriseDB version?
I doubt it. The EDB builds are compiled with VC++ 2008 (for 9.0/9.1).
If you cross-compile with GCC, you'll be using a different vers
On Fri, Jul 13, 2012 at 2:11 PM, Dave Page wrote:
> On Fri, Jul 13, 2012 at 9:31 AM, Atri Sharma wrote:
>> Hi all,
>>
>> I am trying to install my FDW project on windows.I did some research
>> and I believe I shall be requiring pre compiled binaries(dll files).I
>> tried cross compiling using Min
On Fri, Jul 13, 2012 at 9:31 AM, Atri Sharma wrote:
> Hi all,
>
> I am trying to install my FDW project on windows.I did some research
> and I believe I shall be requiring pre compiled binaries(dll files).I
> tried cross compiling using MinGW on my Ubuntu.I am using PGXS for
> compiling and making
Hi all,
I am trying to install my FDW project on windows.I did some research
and I believe I shall be requiring pre compiled binaries(dll files).I
tried cross compiling using MinGW on my Ubuntu.I am using PGXS for
compiling and making my project.I tried overriding CC and setting it
to the MinGW C
Hi all,
Here are some (slightly too long) thoughts about this.
Shaun Thomas skrev 2012-07-12 22:40:
On 07/12/2012 12:02 PM, Bruce Momjian wrote:
Well, the problem also exists if add it as an internal database
feature --- how long do we wait to consider the standby dead, how do
we inform admin
63 matches
Mail list logo
