Andrew Dunstan <[EMAIL PROTECTED]> writes:
> + * Fill in just enough information to set up this perl
> + * function in the safe container and call it.
> + * For some reason not entirely clear, it prevents
> errors that
> +
"Billow Gao" <[EMAIL PROTECTED]> writes:
> Also, when I compile it, I had warning:
> test.c:121: warning: assignment makes pointer from integer without a cast
> The line is:
> tuple = heap_form_tuple( tupdesc, &dtvalues, &isNull );
That part is because you didn't #include access/heapam.h, where
he
Gregory Stark <[EMAIL PROTECTED]> writes:
> "Tom Lane" <[EMAIL PROTECTED]> writes:
>> I didn't do anything about it at the time, but now I am tempted to
>> modify LookupOpclassInfo() so that CLOBBER_CACHE_ALWAYS disables
>> its internal cache. Any objections?
> That sounds not equivalent to recei
Andrew Dunstan wrote:
Andrew Dunstan wrote:
Greg Sabino Mullane wrote:
Just as a followup, I reported this as a bug and it is being looked
at and discussed:
http://rt.perl.org/rt3//Public/Bug/Display.html?id=47576
Appears there is no easy resolution yet.
We might be able to do s
"Tom Dunstan" <[EMAIL PROTECTED]> writes:
> I wouldn't get too worried, though. These are defensive error messages
> that are really just checking for sane input, and they seem difficult
> to deliberately trip, let alone accidentally, so stressing about them
> is probably unnecessary.
Right. I'm
On Nov 28, 2007 11:01 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
> > What is an actual enum type? And how should a user react if he got this
> > message? I would ask, "why not?".
>
> Yeah, I would too, but without a concrete example to look at it's hard
> to say if the situation could be improved.
I don't know if it's the proximate source of your problem but your
MemoryContextSwitchTo() calls are mixed up. You're reusing the same oldcontext
variable for both the switch you're doing in the main body and the switch
you're doing in the inner loop. At the very least you should use two different
On Nov 28, 2007 8:09 PM, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Did you publish it in pgsql-patches? If so, it can be fished from
> there.
Unfortunately, no. IIRC, I believe the topic moved to being
non-user-based quotas and more tablespace-oriented.
--
Jonah H. Harris, Sr. Software Archi
I can return multiple strings w/o problem.
But if I tried to return multiple bytea rows. It only return 10 rows with
empty data.
Please see the code below.
Also, when I compile it, I had warning:
test.c:121: warning: assignment makes pointer from integer without a cast
The line is:
tuple = heap_f
Jonah H. Harris escribió:
> On Nov 28, 2007 3:21 PM, Gevik Babakhani <[EMAIL PROTECTED]> wrote:
> > Sometime ago there was a discussion about user/database quota and
> > IIRC there was also some patch for this (probably got rejected).
> >
> > Does anyone know to which direction we went for having q
On Nov 28, 2007 3:21 PM, Gevik Babakhani <[EMAIL PROTECTED]> wrote:
> Sometime ago there was a discussion about user/database quota and
> IIRC there was also some patch for this (probably got rejected).
>
> Does anyone know to which direction we went for having quotas?
I had written a patch for us
"Tom Lane" <[EMAIL PROTECTED]> writes:
> I didn't do anything about it at the time, but now I am tempted to
> modify LookupOpclassInfo() so that CLOBBER_CACHE_ALWAYS disables
> its internal cache. Any objections?
That sounds not equivalent to receiving a relcache flush at any particular
point in
Magnus Hagander wrote:
Where in the US? We generally list at least the state for ppl int he US
- most often both city+state. (shows up only for people listed as major
developers for the time being, which is why nobody asked for it before)
Denver, CO
Kris Jurka
---(en
On Tue, 27 Nov 2007 23:53:14 -0500 Robert Treat wrote:
> I also think we should be a bit more generous on the EOL notice. Saying one
> more
> update after 8.3 is akin to giving a 1 month EOL notice; not friendly at all
> imo. Set it for July 2008 and I think you have given plenty of notice (and
On Tue, 27 Nov 2007 15:37:04 -0500 Tom Lane wrote:
> "Andreas 'ads' Scherbaum" <[EMAIL PROTECTED]> writes:
> > On Tue, 27 Nov 2007 11:08:58 -0800 Joshua D. Drake wrote:
> >> Release 7.3.21 with and EOL addendum :). E.g; this is the last release
> >> of 7.3 and 7.3 is now considered unsupported.
>
> Uh, he was asking about "quotas", not "quotes". No, we don't
> have user quotas yet.
>
Thank you.
I read we have a "Allow per-tablespace quotas". But the more I think about
this
the more complex it gets. I guess implementing a user quota is a very
different story
than quotas per-tablespace.
On 28/11/2007, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> Pavel Stehule wrote:
> > Hello
> >
> > this patch was commited
> >
> > http://archives.postgresql.org/pgsql-committers/2007-11/msg00530.php
>
> Uh, he was asking about "quotas", not "quotes". No, we don't have user
> quotas yet.
>
I am bli
Pavel Stehule wrote:
> Hello
>
> this patch was commited
>
> http://archives.postgresql.org/pgsql-committers/2007-11/msg00530.php
Uh, he was asking about "quotas", not "quotes". No, we don't have user
quotas yet.
---
>
Hello
this patch was commited
http://archives.postgresql.org/pgsql-committers/2007-11/msg00530.php
Regards
Pavel Stehule
On 28/11/2007, Gevik Babakhani <[EMAIL PROTECTED]> wrote:
> Sometime ago there was a discussion about user/database quota and
> IIRC there was also some patch for this (proba
Hi,
On Mon, 2007-11-26 at 18:01 -0800, John Walker wrote:
> i'd like to try to develop some improvements to psqlodbc.
For development of psqlodbc, please subscribe and post to pgsql-odbc
list.
Regards,
--
Devrim GÜNDÜZ , RHCE
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Andrew Dunstan wrote:
Greg Sabino Mullane wrote:
Just as a followup, I reported this as a bug and it is being looked
at and discussed:
http://rt.perl.org/rt3//Public/Bug/Display.html?id=47576
Appears there is no easy resolution yet.
We might be able to do something with the suggest
On Wednesday 28 November 2007 04:21, Magnus Hagander wrote:
> On Tue, Nov 27, 2007 at 04:08:36PM -0800, Josh Berkus wrote:
> > All,
> >
> > Time for the annual update of this list:
> > http://www.postgresql.org/developer/bios
> >
> > Here's the list of people I gleaned from the release notes (btw,
On Wed, 28 Nov 2007, [EMAIL PROTECTED] wrote:
I consider this matter closed from my point of view and I have modified the
JDBC driver according to my needs.
Could you explain in more detail what you've done to the JDBC driver in
case it is generally useful or other people have the same pro
Sometime ago there was a discussion about user/database quota and
IIRC there was also some patch for this (probably got rejected).
Does anyone know to which direction we went for having quotas?
Regards,
Gevik
Gevik Babakhani
PostgreSQL NL ht
Dave,
> Hiroshi Saito has made a number of smaller but important contributions
> this cycle.
Thanks. I was being surprised to see only one Japanese contributor this
cycle.
> Heikki is from Finland, but currently living in the UK.
Thanks!
> You also missed my name despite it being attributed
Greg Sabino Mullane wrote:
Just as a followup, I reported this as a bug and it is
being looked at and discussed:
http://rt.perl.org/rt3//Public/Bug/Display.html?id=47576
Appears there is no easy resolution yet.
We might be able to do something with the suggested workaround. I will
se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 14:16:16 -0500 (EST)
Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > I believe the reason we don't publicize who is a committer is that
> > we have non-committers who do a lot more for the project. Commit
> > rights are usually given
Bruce Momjian wrote:
> Joshua D. Drake wrote:
> > > I don't have a problem with that, but I think core code committers
> > > and www maintainers should be identified separately.
> >
> > Why? Then we have to also separate advocacy which is just as important
> > and pgfoundry... as well as possibly
Marc G. Fournier wrote:
>
>
> --On Wednesday, November 28, 2007 08:20:04 -0800 "Joshua D. Drake"
> <[EMAIL PROTECTED]> wrote:
>
>>Core <-- this is obvious
>>Committers <-- this is obvious the only question is it only
>> committers to the source tree or do we want to give equal billing t
On 11/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Yes, you support (and worry about) encodings simply because of a C limitation
> dating from 1974, if I recall correctly...
> In Java, for example, a "char" is a very well defined datum, namely a Unicode
> point. While in C it can be some
Joshua D. Drake wrote:
> > I don't have a problem with that, but I think core code committers
> > and www maintainers should be indentified separately.
>
> Why? Then we have to also separate advocacy which is just as important
> and pgfoundry... as well as possibly a host of others. We all have ou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 15:06:58 -0400
"Marc G. Fournier" <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
>
> - --On Wednesday, November 28, 2007 08:20:04 -0800 "Joshua D. Drake"
> <[EMAIL PROTECTED]> wrote:
>
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On Wednesday, November 28, 2007 08:20:04 -0800 "Joshua D. Drake"
<[EMAIL PROTECTED]> wrote:
>Core <-- this is obvious
>Committers <-- this is obvious the only question is it only
> committers to the source tree or do we want to give equ
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Just as a followup, I reported this as a bug and it is
being looked at and discussed:
http://rt.perl.org/rt3//Public/Bug/Display.html?id=47576
Appears there is no easy resolution yet.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key: 0x149
<[EMAIL PROTECTED]> writes:
> Yes, you support (and worry about) encodings simply because of a C limitation
> dating from 1974, if I recall correctly...
> In Java, for example, a "char" is a very well defined datum, namely a Unicode
> point. While in C it can be some char or another (or an error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 13:50:02 -0500
Andrew Dunstan <[EMAIL PROTECTED]> wrote:
> You are being overly sensitive. I never suggested otherwise. I simply
> suggested that the roles people do in fact play should be public.
And I was only pointing to a log
Joshua D. Drake wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 13:15:52 -0500
Andrew Dunstan <[EMAIL PROTECTED]> wrote:
Joshua D. Drake wrote:
Committers <-- this is obvious the only question is it only
committers to the source tree or do we want to give
On 11/28/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On Wednesday 28 November 2007, Trevor Talbot wrote:
> > I'm not entirely sure how that's supposed to solve the client
> > authentication issue though. Demanding that clients present auth data
> > in UTF-8 is no different than demanding t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 12:33:52 -0600
"Kevin Grittner" <[EMAIL PROTECTED]> wrote:
> >>> On Wed, Nov 28, 2007 at 11:34 AM, in message
> >>> <[EMAIL PROTECTED]>,
> Magnus Hagander <[EMAIL PROTECTED]> wrote:
>
> > We don't generally add anybody who just
>>> On Wed, Nov 28, 2007 at 11:34 AM, in message <[EMAIL PROTECTED]>,
Magnus Hagander <[EMAIL PROTECTED]> wrote:
> We don't generally add anybody who just provides a single patch, ever.
> They go in the release notes, but we only add people who've been around
> for a while to this list at all.
On Wed, 28 Nov 2007, Tom Lane wrote:
> Date: Wed, 28 Nov 2007 12:45:30 -0500
> From: Tom Lane <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Cc: pgsql-hackers list
> Subject: Re: [HACKERS] jaguar is up
>
> [EMAIL PROTECTED] writes:
> > Jaguar is a new animal meant to test specific defines as aske
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 13:15:52 -0500
Andrew Dunstan <[EMAIL PROTECTED]> wrote:
>
>
> Joshua D. Drake wrote:
> >Committers <-- this is obvious the only question is it only
> > committers to the source tree or do we want to give equal billing to
> >
On Wednesday 28 November 2007, Alvaro Herrera wrote:
> [EMAIL PROTECTED] escribió:
> > Martijn,
> >
> > :) don't take it personal, I am just trying to obtain confirmation that I
> >
> > understood well the problem. Afterall, it's just that C has a very
> > outdated notion of "char"s (and no notion
Joshua D. Drake wrote:
Committers <-- this is obvious the only question is it only
committers to the source tree or do we want to give equal billing to
the -www guys (I think yes to equal billing)
I don't have a problem with that, but I think core code committers and
www maintainers
On Wednesday 28 November 2007, Trevor Talbot wrote:
> I'm not entirely sure how that's supposed to solve the client
> authentication issue though. Demanding that clients present auth data
> in UTF-8 is no different than demanding they present it in the
> encoding it was entered in originally...
Oh
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Somehow pgindent appears to do odd things with multiline string constants,
> > such as
>
> > somefunc(&blah,
> > "lots of text"
> > "with mulitple lines"
> > "like this");
>
> > Afterwards this looks mo
[EMAIL PROTECTED] writes:
> Jaguar is a new animal meant to test specific defines as asked by Tom
> sometime ago.
> Right now, it compiles and runs with -DCLOBBER_CACHE_ALWAYS
Cool, how long does it take to run the regression tests?
> Let me know if you want me to add/change flags
Awhile bac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 18:34:57 +0100
Magnus Hagander <[EMAIL PROTECTED]> wrote:
> > Now that seems reasonable.
> >
> > Core
> > Regular contributors
> > Occasional contributors
> > Past contributors
> >
> > Core and Regular should be on the same page
Kris Jurka wrote:
>
>
> On Tue, 27 Nov 2007, Josh Berkus wrote:
>
>> Kris Jurka, Finland
>
> USA actually.
Where in the US? We generally list at least the state for ppl int he US
- most often both city+state. (shows up only for people listed as major
developers for the time being, which is why
On 11/28/07, Martijn van Oosterhout <[EMAIL PROTECTED]> wrote:
> On Wed, Nov 28, 2007 at 05:54:05PM +0200, [EMAIL PROTECTED] wrote:
> > Regarding the problem of "One True Encoding", the answer seems obvious to
> > me:
> > use only one encoding per database cluster, either UTF-8 or UTF-16 or
> >
Joshua D. Drake wrote:
> On Wed, 28 Nov 2007 16:53:43 +
> Dave Page <[EMAIL PROTECTED]> wrote:
>
>> Joshua D. Drake wrote:
>>> On Wed, 28 Nov 2007 16:27:42 +
>>> Dave Page <[EMAIL PROTECTED]> wrote:
>>>
Why not Hackers? Noone is a 'member' of anything except core or
mayber the we
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Somehow pgindent appears to do odd things with multiline string constants,
> such as
> somefunc(&blah,
> "lots of text"
> "with mulitple lines"
> "like this");
> Afterwards this looks more like this:
> somefunc(&blah,
>
Tom Lane wrote:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> Whether there's any need to support the old protocol in the server depends on
>> whether there are any clients out there which use it which is harder to
>> determine and not affected by whether Postgres 7.3 is still around.
>
> Right.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 16:53:43 +
Dave Page <[EMAIL PROTECTED]> wrote:
> Joshua D. Drake wrote:
> > On Wed, 28 Nov 2007 16:27:42 +
> > Dave Page <[EMAIL PROTECTED]> wrote:
> >
> >> Why not Hackers? Noone is a 'member' of anything except core or
Joshua D. Drake wrote:
> On Wed, 28 Nov 2007 16:27:42 +
> Dave Page <[EMAIL PROTECTED]> wrote:
>
>> Why not Hackers? Noone is a 'member' of anything except core or mayber
>> the web/infrastructure team.
>
> Define Hacker. And I could argue that some are members of PGDG.
Says he who only the
On Wed, Nov 28, 2007 at 05:54:05PM +0200, [EMAIL PROTECTED] wrote:
> Regarding the problem of "One True Encoding", the answer seems obvious to me:
> use only one encoding per database cluster, either UTF-8 or UTF-16 or another
> Unicode-aware scheme, whichever yields a statistically smaller datab
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 16:27:42 +
Dave Page <[EMAIL PROTECTED]> wrote:
> Actually we've previously agreed (in -core) that we do not want to
> list committers for various reasons. Yeah, I know the list isn't too
> hard to figure out, but we don't want
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> On Wed, 28 Nov 2007 13:58:27 +
> Gregory Stark <[EMAIL PROTECTED]> wrote:
>
>> "Gregory Stark" <[EMAIL PROTECTED]> writes:
>>
>> > "Josh Berkus" <[EMAIL PROTECTED]> writes:
>> >
>> >> All,
>> >>
>> >> Time for the annual update of this list:
>>
Jaguar is a new animal meant to test specific defines as asked by Tom
sometime ago.
Right now, it compiles and runs with -DCLOBBER_CACHE_ALWAYS
Let me know if you want me to add/change flags
Best regards
--
Olivier PRENANT Tel: +33-5-61-50-97-00 (Work)
15, Chemin des Monges
Joshua D. Drake wrote:
> Not to mention there don't seem to be any defined rules. I asked Berkus
> and his reply was, "It has always been a little fuzzy". I asked Devrim
> and he gave me 5 bullet points that don't quite make sense.
Not sure what Devrim is referring to, but most often in the past R
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 13:58:27 +
Gregory Stark <[EMAIL PROTECTED]> wrote:
> "Gregory Stark" <[EMAIL PROTECTED]> writes:
>
> > "Josh Berkus" <[EMAIL PROTECTED]> writes:
> >
> >> All,
> >>
> >> Time for the annual update of this list:
> >>...
> >> Gr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 13:30:55 +
Gregory Stark <[EMAIL PROTECTED]> wrote:
> Alexandru Cârstoiu <[EMAIL PROTECTED]> writes:
>
> > This tells me that the v3 protocol appeared at 7.4, so there's no
> > need to support v2 in future database versions (s
On Wed, Nov 28, 2007 at 12:24:26PM -0300, Alvaro Herrera wrote:
> Martijn van Oosterhout wrote:
> > On Wed, Nov 28, 2007 at 11:57:35AM -0300, Alvaro Herrera wrote:
> > > Can we do something like this to report the Win32 error code so that the
> > > user has a higher chance of figuring out what's go
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 28 Nov 2007 09:46:36 +
Dave Page <[EMAIL PROTECTED]> wrote:
> I should also point out that the contributor list has always included
> people who have contributed to non-core community projects in the past
> as well - psqlODBC, the JDBC dr
[EMAIL PROTECTED] escribió:
> Martijn,
>
> :) don't take it personal, I am just trying to obtain confirmation that I
> understood well the problem. Afterall, it's just that C has a very outdated
> notion of "char"s (and no notion of Unicode). I was naively under the
> impression that "char"s ha
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> There are a few error messages like this in the code:
> /*
> * We rely on being able to get the specific enum type from the
> calling
> * expression tree. The generic type mechanism should have ensured
> that
> * b
It looks like a corrupted-data kind of problem. Can you extract
a reproducible test case?
The problem was the hardware!!
On a second system (Mac Power G5) there was no failure, i.e. the
error is not reproducible.
Thanks for your help.
Rudolf VanderLeeden
---(end o
Martijn,
:) don't take it personal, I am just trying to obtain confirmation that I
understood well the problem. Afterall, it's just that C has a very outdated
notion of "char"s (and no notion of Unicode). I was naively under the
impression that "char"s have evolved in nowadays C.
Regarding the
On Wed, Nov 28, 2007 at 10:45:31AM -0500, Tom Lane wrote:
> Louis-David Mitterrand <[EMAIL PROTECTED]> writes:
> > I am seeing this error with 8.3beta3 on debian unstable:
>
> > 2007-11-28 15:15:46 CET ERROR: cached plan must not change result type
>
> > Let me know if you need more info.
>
Louis-David Mitterrand <[EMAIL PROTECTED]> writes:
> I am seeing this error with 8.3beta3 on debian unstable:
> 2007-11-28 15:15:46 CET ERROR: cached plan must not change result type
> Let me know if you need more info.
Yes.
regards, tom lane
Hi,
I am seeing this error with 8.3beta3 on debian unstable:
2007-11-28 15:15:46 CET ERROR: cached plan must not change result type
2007-11-28 15:15:46 CET STATEMENT: SELECT s.*,
coalesce(d.firstname||' ','')||coalesce(d.lastname,'') as person_na
On Tue, Nov 27, 2007 at 06:03:46PM +, Simon Riggs wrote:
> Just wanted to review a few thoughts and ideas around improving external
> sorts, as recently encouraged to do by Jim Nasby.
Is there any way of PG knowing that having an index on a subset of the
sorted columns is sometimes a win? Fo
Martijn van Oosterhout wrote:
> On Wed, Nov 28, 2007 at 11:57:35AM -0300, Alvaro Herrera wrote:
> > Can we do something like this to report the Win32 error code so that the
> > user has a higher chance of figuring out what's going on?
>
> The Windows API provides a way to get the error message ass
On Wed, Nov 28, 2007 at 11:39:33AM +0200, [EMAIL PROTECTED] wrote:
> During the authentication phase, no such conversion takes place - you were
> right and I couldn't believe it! In the case when your database name, your
> user name or password contain non-ASCII characters, you're out of luck if
On Wed, Nov 28, 2007 at 11:57:35AM -0300, Alvaro Herrera wrote:
> Can we do something like this to report the Win32 error code so that the
> user has a higher chance of figuring out what's going on?
The Windows API provides a way to get the error message associated
with the code. It seems it would
Gregory Stark <[EMAIL PROTECTED]> writes:
> Whether there's any need to support the old protocol in the server depends on
> whether there are any clients out there which use it which is harder to
> determine and not affected by whether Postgres 7.3 is still around.
Right. There's really not much
On Wednesday 28 November 2007, Gregory Stark wrote:
> > This tells me that the v3 protocol appeared at 7.4, so there's no need to
> > support v2 in future database versions (starting with 8.3?). It would
> > simplify code in interfaces like JDBC too.
>
> I think the second half of this is correct.
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> FYI, at this time only the German and French translations have been
> updated almost fully, and none of them is yet 100% in the backend
> translation. I think it's appropriate to mark this string for
> translation at this time (i.e. turn it into an erep
Hi,
We've seen several cases of people (running 8.1 or 8.2) that see
messages like this:
2007-11-26 11:41:59 ERROR: could not open relation 1663/352369/353685: Invalid
argument
The platform is Win32.
The problem is that pgwin32_open reduces any error code from
GetLastError that's not ERROR_PA
Brendan Jurd escribió:
> If the only reason for keeping A_Const->typename around is the alleged
> code saving (as indicated by the code comments), my offer to do away
> with it is still on the table.
Code cleanup is always welcome.
--
Alvaro Herrera Developer, http://ww
"Gregory Stark" <[EMAIL PROTECTED]> writes:
> "Josh Berkus" <[EMAIL PROTECTED]> writes:
>
>> All,
>>
>> Time for the annual update of this list:
>>...
>> Greg Stark, USA
>
> I'm not sure what the countries are supposed to signify but that's neither the
> country I hail from nor where I'm currently
Alexandru Cârstoiu <[EMAIL PROTECTED]> writes:
> This tells me that the v3 protocol appeared at 7.4, so there's no need to
> support v2 in future database versions (starting with 8.3?). It would
> simplify code in interfaces like JDBC too.
I think the second half of this is correct. There would
I'm not a developper, but it occured to me that you should consider dropping
the support for client-server wire protocol v2.
I quote a comment I found in JDBC driver's code:
// NOTE: To simplify this code, it is assumed that if we are
// using the V3 protocol, then the database i
I'm not a developper, but it occured to me that you should consider dropping
the support for client-server wire protocol v2.
I quote a comment I found in JDBC driver's code:
// NOTE: To simplify this code, it is assumed that if we are
// using the V3 protocol, then the database i
Tom Lane napsal(a):
Comments, opinions?
Is it time to remove old communication protocol support and cleanup code in 8.4?
Zdenek
---(end of broadcast)---
TIP 6: explain analyze is your friend
There are a few error messages like this in the code:
/*
* We rely on being able to get the specific enum type from the calling
* expression tree. The generic type mechanism should have ensured that
* both are of the same type.
*/
enumtypoid = g
Bruce Momjian wrote:
> I have applied the attached patch to change the NOTICE to ERROR. Thanks
> for spotting this.
FYI, at this time only the German and French translations have been
updated almost fully, and none of them is yet 100% in the backend
translation. I think it's appropriate to mark
Somehow pgindent appears to do odd things with multiline string constants,
such as
somefunc(&blah,
"lots of text"
"with mulitple lines"
"like this");
Afterwards this looks more like this:
somefunc(&blah,
"lots of text"
"with mulitple lines"
"like
I ask you to implement ideas, stated in
http://sql2008.euro.ru/sql2008.ppt
(description is in http://sql2008.euro.ru/zip/sql2008-allfiles.zip)
in Postgres.
I'm ready to aswer to any your questions.
Dmitry Turin
---(end of broadcast)---
TIP 1: if p
I ask you to implement ideas, stated in
http://sql2008.euro.ru/sql2008.ppt
(description is in http://sql2008.euro.ru/zip/sql2008-allfiles.zip)
in MySql.
I'm ready to aswer to any your questions.
Dmitry Turin
---(end of broadcast)---
TIP 6: explain
Stefan Kaltenbrunner wrote:
> yeah well - the release notes do not make that good a reference on the
> "who submitted patches" question anyway because the do not contain stuff
> that are mere compile failures or add support for additional
> platforms/cleanups) of new features (ie my patches to add
Ok, that's bad. I've also read crypt.c and md5.c.
And what a nightmare is C compared to Java (granted, there's a difference in
age of more than 20 years).
My guess is that since the "char" type is one byte long, all "char *"
expressions are actually pointers to array of bytes which are transmitt
Dave Page wrote:
Josh Berkus wrote:
All,
Time for the annual update of this list:
http://www.postgresql.org/developer/bios
Here's the list of people I gleaned from the release notes (btw, if people
have countries for the folks who aren't attributed, I'd appreciate them).
Of course, there ar
On Tue, 27 Nov 2007, Simon Riggs wrote:
My vision for that is a set of tests that test very specific aspects of
code, much the same way as the regression tests attempt feature
coverage. Examples would be
- 1 INSERTs
- 1 INSERTs using multi-VALUEs clauses
- 10 rows inserted by COPY
-
On Tue, Nov 27, 2007 at 04:08:36PM -0800, Josh Berkus wrote:
> All,
>
> Time for the annual update of this list:
> http://www.postgresql.org/developer/bios
>
> Here's the list of people I gleaned from the release notes (btw, if people
> have countries for the folks who aren't attributed, I'd app
Josh Berkus wrote:
> All,
>
> Time for the annual update of this list:
> http://www.postgresql.org/developer/bios
>
> Here's the list of people I gleaned from the release notes (btw, if people
> have countries for the folks who aren't attributed, I'd appreciate them).
> Of course, there are ma
IMHO, it may not be a bad idea to list countries , it shows the diversity of
the community.
-Original Message-
From: "Gregory Stark" <[EMAIL PROTECTED]>
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Cc: "pgsql-hackers@postgresql.org" ; "[EMAIL
PROTECTED]" <[EMAIL PROTECTED]>
Sent: 28/11/20
Hi,
On Tue, 2007-11-27 at 14:26 -0500, Tom Lane wrote:
> > I assume you no longer need to maintain it for Redhat then?
>
> Well, I still do, nominally, but RHEL-3 is in maintenance mode
> (meaning no more scheduled updates). It would take a fairly serious
> bug to get Red Hat's attention to the
98 matches
Mail list logo
