> lo_import_with_oid added.
>
> Note that actually committed function signature is:
>
> Oid lo_import_with_oid(PGconn *conn, const char *filename, Oid lobjId);
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
It seems I forgot about the serer side lo_import. Included are the
patches to add new form of
hi NikhilS.
2008/3/14, NikhilS <[EMAIL PROTECTED]>:
>
> Hi Longlong,
>
>
> > > i think this is a better idea.
> > from *NikhilS *
> > http://archives.postgresql.org/pgsql-hackers/2007-12/msg00584.php
> > But instead of using a per insert or a batch insert substraction, I am
> > thinking that we ca
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
> One of the questions in the original patch submission was whether it
> would be worth changing all those DirectFunctionCall(textin) and
> (textout) calls to use the new functions. Is it worthwhile avoiding
> the fmgr overhead?
I think that's worth doin
I know you are i a C state but,
A string plus a NULL string is A string
mandi TOM
Mark Mielke wrote
> This returns to the question of whether count of the whole table is useful,
> or whether
> count of a GROUP BY or WHERE is useful.
> If GROUP BY or WHERE is useful, then trigger on UPDATE becomes necessary.
True... for the example I gave I should have had an update trigger on
On 20/03/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
>
> I started to look at applying this patch and immediately decided that
> I didn't like these names --- it's exceeding un-obvious which direction
> of conversion any one of the functions performs. Seems like every time
> you wanted to call on
Magnus Hagander wrote:
Andrew Dunstan wrote:
Robert Lor wrote:
Peter Eisentraut wrote:
Well, yes. I meant to say, a build system that can supply the
functionality of Gen_fmgrtab can surely implement this new thing.
I see there is Perl being used, so it should be simple.
I was thinkin
Volkan YAZICI <[EMAIL PROTECTED]> writes:
> But I'd vote for TextPGetCString style Tom suggested for the eye-habit
> compatibility with the rest of the code.
If there are not additional votes, I'll go with TextPGetCString
and CStringGetTextP.
regards, tom lane
--
Sent vi
Richard Huxton <[EMAIL PROTECTED]> writes:
> Missed the mailing list on the last reply
>> patrick wrote:
>>> thoses queries are not working, same message:
>>> ERROR: invalid byte sequence for encoding "UTF8": 0xc3
>>>
>>> what i found is in postgresql.conf if i change:
>>> default_text_search_confi
Andrew Dunstan wrote:
Robert Lor wrote:
Peter Eisentraut wrote:
Well, yes. I meant to say, a build system that can supply the
functionality of Gen_fmgrtab can surely implement this new thing. I
see there is Perl being used, so it should be simple.
I was thinking of using a Perl script t
On Tue, Mar 18, 2008 at 07:23:40PM +0100, Peter Eisentraut wrote:
> Am Dienstag, 18. März 2008 schrieb Bruce Momjian:
> > Peter Eisentraut wrote:
> > > Log Message:
> > > ---
> > > Don't need -Wno-error anymore, because flex is no longer producing
> > > warnings.
> >
> > I see this patch on
On Wed, 2008-03-19 at 12:24 -0400, Tom Lane wrote:
> > [ sinval lock management needs redesign ]
>
> Yup it does.
I wrote a redesigned, simplified version of my earlier patch. Enclosed
here for discussion only, not expecting this to be the final version.
Comments at top of patch explain it.
The
Robert Lor wrote:
Peter Eisentraut wrote:
Well, yes. I meant to say, a build system that can supply the
functionality of Gen_fmgrtab can surely implement this new thing. I
see there is Perl being used, so it should be simple.
I was thinking of using a Perl script to generate the dummy he
On Wed, 19 Mar 2008, Sam Mason <[EMAIL PROTECTED]> writes:
> ...
> char * str = cstring_of_text(src_text);
> ...
>
> I think I got my original inspiration for doing it this way around from
> the Caml language.
Also, used in Common Lisp as class accessors:
char *s = cstring_of(text);
text *t
On Wed, Mar 19, 2008 at 12:51:35PM -0400, Tom Lane wrote:
> "Brendan Jurd" <[EMAIL PROTECTED]> writes:
> > char * text_cstring(const text *t)
>
> What do people think of text_to_cstring?
I tend to put things the other way around in my code, i.e:
char * cstring_of_text(const text *t)
mainly be
On Mon, Mar 17, 2008 at 11:26:59AM +, Mike Aubury wrote:
> Add a function to return the current PGConn used within ecpg..
I still consider such a feature is a little bit hackish, but I also
think Mike has some valid points. And given that adding this patch does
not create side effects I will c
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
> As discussed on -hackers, I'm trying to get rid of some redundant code
> by creating a widely useful set of functions to convert between text
> and C string in the backend.
> The new extern functions, declared in include/utils/builtins.h and
> defined i
Simon Riggs <[EMAIL PROTECTED]> writes:
> I've completed a review of all of the LWlocking in the backends. This is
> documented in the enclosed file. I would propose that we use this as
> comments in lwlock.h or in the README, if people agree.
I don't think that putting this list in as documentati
"Nikolay Samokhvalov" <[EMAIL PROTECTED]> writes:
> 1. Is it correct at all to use SRF in select list, w/o explicit FROM?
You can read about the current behavior in ExecTargetList, but basically
the idea is to cycle all the SRFs until they all say "done" at the same
time. So the number of result
Hi,
> Good. I'll bring the patch up to date with HEAD.
Did you post an updated patch to HEAD?
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To m
On Wed, 19 Mar 2008, "Nikolay Samokhvalov" <[EMAIL PROTECTED]> writes:
> I wonder, if the following is correct and provides expected result:
>
> test=# select generate_series(1, 2), generate_series(1, 4);
> generate_series | generate_series
> -+-
>1
Le mercredi 19 mars 2008, Albert Cervera i Areny a écrit :
Hi !
> A Dimecres 19 Març 2008, Nikolay Samokhvalov va escriure:
> > 2. Why the query above provides 4 rows, not 2*4=8? Actually, that's
> > interesting -- I can use this query to find l.c.m. But it's defenetely
> > not that I'd expect be
Peter Eisentraut napsal(a):
Zdenek Kotala wrote:
But how it was mentioned in this thread maybe
somethink like this "CREATE TABLESPACE name LOCATION '/my/location'
SEGMENTS 10GB" should good solution. If segments is not mentioned then
default value is used.
I think you would need a tool to rese
A Dimecres 19 Març 2008, Nikolay Samokhvalov va escriure:
> 2. Why the query above provides 4 rows, not 2*4=8? Actually, that's
> interesting -- I can use this query to find l.c.m. But it's defenetely
> not that I'd expect before my try...
2*4 = 8:
select * from generate_series(1, 2) a, generat
On Wed, Mar 19, 2008 at 10:51:12AM +0100, Martijn van Oosterhout wrote:
> On Wed, Mar 19, 2008 at 09:38:12AM +0100, Peter Eisentraut wrote:
> > Another factor I just thought of is that tar, commonly used as part of a
> > backup procedure, can on some systems only handle files up to 8 GB in size.
Hi,
I wonder, if the following is correct and provides expected result:
test=# select generate_series(1, 2), generate_series(1, 4);
generate_series | generate_series
-+-
1 | 1
2 | 2
1 |
On Tue, 2008-03-18 at 21:26 +0700, Artem Yazkov wrote:
> Restrictions:
> 1. Uninterrupted supply of statistics collector necessary for
> efficient use of this algorithm.
In my understanding, we do not guarantee this. That leaves the rest of
your ideas drifting, I'm sorry to say. Your ide
On Wed, Mar 19, 2008 at 09:38:12AM +0100, Peter Eisentraut wrote:
> Another factor I just thought of is that tar, commonly used as part of a
> backup procedure, can on some systems only handle files up to 8 GB in size.
> There are supposed to be newer formats that can avoid that restriction, but
Hi hackers,
I'm novice in PostgreSQL codebase (and in English too :-)), but I'd be
glad to make a modest contribution to this great project.
By viewing this list, I see a lot of discussions on the problem of
"fast count (*)", but acceptable decision have not been formulated.
Well, I make
Zdenek Kotala wrote:
> But how it was mentioned in this thread maybe
> somethink like this "CREATE TABLESPACE name LOCATION '/my/location'
> SEGMENTS 10GB" should good solution. If segments is not mentioned then
> default value is used.
I think you would need a tool to resegmentize a table or tabl
What locale do you use? It seems that problem is in collation. Try it with C.
Zdenek
Pavel Stehule napsal(a):
Hello
I tested head again from scratch with negative results:
http://www.pgsql.cz/data/regression.diffs
http://www.pgsql.cz/data/regression.out
Regards
Pavel Stehule
Pavel Stehule wrote:
I tested head again from scratch with negative results:
There's a bunch of errors like this in there:
+ ERROR: could not open file
"/home/pavel/src/pgsql/src/test/regress/results/onek.data" for writing:
Permission denied
Seems like a permission problem... Not sure if
Hello
I tested head again from scratch with negative results:
http://www.pgsql.cz/data/regression.diffs
http://www.pgsql.cz/data/regression.out
Regards
Pavel Stehule
[EMAIL PROTECTED] pgsql]$ uname -a
Linux nemesis.nat.buk.cvut.cz 2.6.24.3-34.fc8 #1 SMP Wed Mar 12
18:17:20 EDT 2008 i686 i686 i
Artem Yazkov <[EMAIL PROTECTED]> writes:
> By viewing this list, I see a lot of discussions on the problem of
> "fast count (*)", but acceptable decision have not been formulated.
> Well, I make bold to propose own view on the problem.
A number of the things you suggest would be good
34 matches
Mail list logo
