On Thu, 6 Nov 2008, "xie jiong" <[EMAIL PROTECTED]> writes:
> what's mean of pageno? or what 's "page" of a large object refer to?
> is this "page"(pageno) refer to "chunk"(chunk number) of lob, as
> opposed to real data page? (or just one data page to store one chunk
> of lob)
Checked the explana
"M. Edward (Ed) Borasky" <[EMAIL PROTECTED]> writes:
> Someone at the PostgreSQL West conference last weekend expressed an
> interest in a Lisp procedural language. The only two Lisp environments
> I've found so far that aren't GPL are Steel Bank Common Lisp (MIT,
> http://sbcl.sourceforge.net) and
On Fri, 19 Sep 2008, "Gevik Babakhani" <[EMAIL PROTECTED]> writes:
> Has there been any idea to port PG to a more modern programming language
> like C++? Of course there are some minor obstacles like a new OO design,
> this being a gigantic task to perform and rewriting almost everything etc...
> I
On Tue, 9 Sep 2008, David Fetter <[EMAIL PROTECTED]> writes:
>> AFAICS, PostgreSQL is not keeping info about when a table, database,
>> sequence, etc was created. We cannot get that info even from OS,
>> since CLUSTER or VACUUM FULL may change the metadata of
>> corresponding relfilenode.
>
> When
On Mon, 8 Sep 2008, Alvaro Herrera <[EMAIL PROTECTED]> writes:
>> Modified as you suggested. BTW, will there be a similar i18n scenario
>> for "dropped column" you mentioned below?
>
> Yes, you need _() around those too.
For this purpose, I introduced a dropped_column_type variable in
validate_tup
On Fri, 05 Sep 2008, Tom Lane <[EMAIL PROTECTED]> writes:
> I think the best way is to use
>
> subroutine(..., gettext_noop("special error message here"))
>
> at the call sites, and then
>
> errmsg("%s", _(msg))
>
> when throwing the error. gettext_noop() is needed to have the string
>
On Fri, 5 Sep 2008, Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Please use the patch I posted yesterday, as it had all the issues I
> found fixed. There were other changes in that patch too.
My bad. Patch is modified with respect to suggestions[1][2] from
Tom. (All 115 tests passed in cvs tip.)
On Thu, 04 Sep 2008, Tom Lane <[EMAIL PROTECTED]> writes:
> This is not ready to go: you've lost the ability to localize most of
> the error message strings.
How can I make this available? What's your suggestion?
> Also, "char *msg" should be "const char *msg"
Done.
> if you're going to pass li
On Thu, 4 Sep 2008, Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Cool, thanks. I had a look and you had some of the expected vs.
> returned reversed.
I'll happy to fix the reversed ones if you can report them in more
details.
Regards.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@post
[Please ignore the previous reply.]
On Fri, 8 Aug 2008, Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I think this is a good idea, but the new error messages need more work.
> Have a look at the message style guidelines please,
> http://www.postgresql.org/docs/8.3/static/error-style-guide.html
Rig
On Fri, 8 Aug 2008, Alvaro Herrera <[EMAIL PROTECTED]> writes:
> I think this is a good idea, but the new error messages need more work.
> Have a look at the message style guidelines please,
> http://www.postgresql.org/docs/8.3/static/error-style-guide.html
Right. Done -- I hope.
> Particularly I
Hi,
Yesterday I needed to fiddle with PostgreSQL internals to be able to
debug a PL/pgSQL procedure returning a set of records. I attached the
patch I used to increase the verbosity of error messages related with
function return type checks. I'll be appreciated if any developer could
commit this p
Hi,
[I've searched archives for the subject, but couldn't find a related
discussion. If there is any, sorry for duplication.]
We're migrating nearly a dozen of MSSQL servers of size ~100GiB per
cluster. For this purpose, we dump MSSQL data to COPY files using a Java
program. We have database sche
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, 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
Hi,
In an address search framework of a company, we need to deal with
queries including potential spelling errors. After some external
address space constraints (e.g. match first letters, word length,
etc.) we're still ending up with a huge data set to filter through
Levenshtein like distance metr
On Oct 26 05:27, Volkan YAZICI wrote:
> On Oct 26 03:33, FAST PostgreSQL wrote:
> > I couldn't find the CONSTRAINT name ('testconstraint' in this case) being
> > stored in the system catalog. Any idea where I can find it?
>
> AFAIK, it is passed to the related
On Oct 26 03:33, FAST PostgreSQL wrote:
> I couldn't find the CONSTRAINT name ('testconstraint' in this case) being
> stored in the system catalog. Any idea where I can find it?
AFAIK, it is passed to the related procedure via a DomainIOData struct
that fcinfo->flinfo->fn_extra points to. (See do
On Oct 21 05:09, Michael Fuhr wrote:
> I hadn't noticed the TODO item but about a year ago I posted a
> cursor_plan_rows() function and asked for comments.
Ah! I didn't see this.
> The only reply was from Tom, who said, "Given how far off it
> frequently is, I can't believe that any of the people
Hi,
I'm trying to implement estimated_count() function that's mentioned in
the TODO list. First of all, I wanted to learn if this TODO item is
still valid? I looked at the related -hackers discussions, does anybody
want to say more sth related with the implementation?
Also I've some questions. I'
Hi,
While returning from a function call, PL can easily interfere will be
returned HeapTuple's TupleDesc from fcinfo. But what if function returns
a record type? Then we must create our own TupleDesc (or AttInMetadata)
for the related attribute (and then create HeapTuple). So far everything
is ok,
On Oct 05 03:34, Tom Lane wrote:
> Volkan YAZICI <[EMAIL PROTECTED]> writes:
> > When I allocate a new memory context via
>
> > oldmcxt = AllocSetContextCreate(TopMemoryContext, ...)
> > persistent_mcxt = CurrentMemoryContext;
>
> ITYM
>
>
Hi,
When I allocate a new memory context via
oldmcxt = AllocSetContextCreate(TopMemoryContext, ...)
persistent_mcxt = CurrentMemoryContext;
How can I store the persistent_mcxt in a persistent place that I'll be
able to reach it in my next getting invoked? Is that possible? If not,
how can I
Hi,
I was using OidInputFunctionCall() to cast a basic type into a domain
type. But when I saw
/*
* As above, for I/O functions identified by OID. These are only to be
* used in seldom-executed code paths. They are not only slow but leak
* memory.
*/
Datum
OidInputFunctionCall(Oid functionI
On Aug 17 10:38, Tom Lane wrote:
> Volkan YAZICI <[EMAIL PROTECTED]> writes:
> > I've still biten by a single "write past chunk" error while returning a
> > record in PL/scheme:
>
> > WARNING: problem in alloc set ExprContext: detected write p
On Aug 16 04:20, Volkan YAZICI wrote:
> On Aug 16 03:09, Volkan YAZICI wrote:
> > WARNING: problem in alloc set ExprContext: detected write past chunk
> > end in block 0x8462f00, chunk 0x84634c8
> > WARNING: cache reference leak: cache pg_type (34), tuple 2/7 has
> >
On Aug 16 11:37, Tom Lane wrote:
> Volkan YAZICI <[EMAIL PROTECTED]> writes:
> > On Aug 11 12:51, Greg Sabino Mullane wrote:
> >> Prepared statements are not visible nor survivable outside of your
> >> session, so this doesn't really make sense. If your appl
On Aug 16 03:09, Volkan YAZICI wrote:
> WARNING: problem in alloc set ExprContext: detected write past chunk
> end in block 0x8462f00, chunk 0x84634c8
> WARNING: cache reference leak: cache pg_type (34), tuple 2/7 has
> count 1
Excuse me for bugging the list. I've solved the
Hi,
I've been trying to implement INOUT/OUT functionality in PL/scheme. When
I return a record type tuple, postmaster complains with below warnings:
WARNING: problem in alloc set ExprContext: detected write past chunk
end in block 0x8462f00, chunk 0x84634c8
WARNING: cache reference leak: cache
On Aug 11 12:51, Greg Sabino Mullane wrote:
> > think it would be quite handy to be able to gather information about
> > a prepared stmt in later phases of an application. For instance one
> > might need to get the parameter and row types of a prepared query
> > that he/she isn't created.
>
> Prep
Hi,
What's [the difference between] a record (which is a pseudo 'p' type) and
a rowtype (which's a complex 'c' type).
Regards.
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Aug 10 11:35, Tom Lane wrote:
> Volkan YAZICI <[EMAIL PROTECTED]> writes:
> > [ patch to add PQdescribePrepared and PQdescribePortal ]
>
> After looking this over, I don't see the point of PQdescribePortal,
> at least not without adding other functiona
On Jun 16 08:21, Tom Lane wrote:
> Bruce Momjian writes:
> > Volkan YAZICI wrote:
> >> The problem is, AFAICS, it's not possible to distinguish between a tuple
> >> returning query (T, ..., C, Z or T, E) and a description of a portal (T,
> >>
On Jun 13 10:20, Bruce Momjian wrote:
>
> Good point. The number of CSV options would be hard to support for
> pg_dump. Any thoughts from anyone on how to do that cleanly? Could we
> just support the default behavior?
IMHO, it might be better if we'd support a syntax like
pg_dump --csv=opt0
On May 19 11:51, [EMAIL PROTECTED] wrote:
> if (PQsendQuery(conn, "COPY test FROM STDIN") > 0) {
> retrieve(conn, 20);
Shouldn't you be send()'ing instead of retrieve()'ing? COPY tbl FROM
stdin, requests data from client to COPY FROM stdin TO tbl.
Regards.
---(end
Hi,
First, thanks so much for your reply.
On May 10 04:01, Teodor Sigaev wrote:
> > Again, in g_int_decompress(), I couldn't figure out the functionality of
> > below lines:
>
> gist__int_ops use rangeset compression technique, read about in "THE
> RD-TREE: AN INDEX STRUCTURE FOR SETS", Joseph
IIRC, "Update pg_dump and psql to use the new COPY libpq API" TODO
item's goal is already achieved in the cvs tip.
Regards.
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Hi,
[Sending this message (first) to -hackers for discussion about the
extension and followed implementation.]
On Apr 01 09:39, Volkan YAZICI wrote:
> I've prepared a patch for the Describe <-> ParameterDescription
> messaging which is available via current extended query pr
Hi,
On Mar 25 08:47, John DeSoi wrote:
> I have not looked at libpq in any detail, but it should have access
> to the type of all the parameters in the prepared statement. The
> Describe (F) statement in the frontend/backend protocol identifies
> the type of each parameter.
I've prepared a
Hi,
On Mar 08 04:08, Bruce Momjian wrote:
> I have applied all the patches in the patch queue, and am starting to
> look at the patches_hold queue, which are patches submitted after the
> feature freeze.
Related with
BUG #1931: ILIKE and LIKE fails on Turkish locale
Case Conversion Fix for M
Hi,
While trying to initdb using cvs tip, it dumps below error output:
...
creating configuration files ... ok
creating template1 database in pgd/base/1 ...
FATAL: failed to initialize TimeZone to "UNKNOWN"
child process exited with exit code 1
...
I edited some files but don't thin
Hi,
There're lots of places in the code which uses either pg_tolower()
or just tolower() - without aware of MB characters; or some
on-their-own implementations of pg_tolower(). (Actually, AFAIK,
whole MB case conversion is broken in -rHEAD.)
For instance, consider backend/utils/adt/{like.c, like_
On Dec 16 08:47, Bruce Momjian wrote:
> I think an int64 is the proper solution. If int64 isn't really
> 64-bits, the code should still work though.
(I'd prefer uint64 instead of an int64.) In src/include/c.h, in
this or that way it'll assign a type for uint64, so there won't
be any problem for bo
I prepared a patch for "Have COPY return the number of rows
loaded/unloaded?" TODO. (Sorry for disturbing list with such a simple
topic, but per warning from Bruce Momjian, I send my proposal to -hackers
first.)
I used the "appending related information to commandTag" method which is
used for INSE
On Dec 08 04:36, Kai wrote:
> After working regularly with inet values in sql, it would be nice to be able
> to do this:
>
> => select '192.168.1.1'::inet + 1 as result;
> result
> -
>192.168.1.2
> (1 row)
You may take a look at ip4r[1] project t
Related TODO paragraph:
«Prevent PQfnumber() from lowercasing unquoted the column name.
PQfnumber() should never have been doing lowercasing, but historically
it has so we need a way to prevent it.»
PQfnumber() Fix Proposal
In the current version of PQfnumber(), i
Hi,
I'm trying to understand the schema laying behind
backend/utils/adt/like.c to downcase letters [1]. When I look at the
other tolower() implementations, there're lots of them spread around.
(In interfaces/libpq, backend/regex, backend/utils/adt/like and etc.)
For example, despite having pg_wc_t
Hi,
On 10/13/05, Tom Lane <[EMAIL PROTECTED]> wrote:
> Really, PQfnumber shouldn't do any case folding at all; that's not in
> its charter if you ask me. The problem is how to get there from here
> without too much compatibility pain. Maybe invent a new routine that
> does it right and then depr
On 10/12/05, Bruce Momjian wrote:
> The question mark means we are not sure how to deal with it. I think
> your idea of using quotes to preserve case is a good one.
I think related TODO is added for that gotcha which was written in
PQfnumber() comments in fe-exec.c: «Downcasing in the frontend m
Hi,
Which way do you suggest to "Prevent libpq's PQfnumber() from
lowercasing the column name" (which is listed as a TODO item). If
column name has quotes around it we're just removing the quotes and
comparing with the related column name. Else, lowercasing the column
name and then comparing.
I c
On 7/15/05, Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> > You're mentioning about PHP PostgreSQL API, right?
>
> No, I'm talking about a PostgreSQL backend function.
Sorry, when you give a name like pg_get_prepared() (which is used in
PHP PostgreSQL API functions), I thought it's for PHP
Hi,
On 7/15/05, Christopher Kings-Lynne <[EMAIL PROTECTED]> wrote:
> Would it be useful to have a pg_get_prepared(name) function that returns
> true or false depending on whether or not there is a prepared query of
> that name?
(You're mentioning about PHP PostgreSQL API, right?) I couldn't see
a
Hi,
On 5/19/05, Tom Lane <[EMAIL PROTECTED]> wrote:
> 8.0.2 and up should provide/require libpq.so.4 and so on. Apparently
> there is something broken with this set of RPMs.
For futher of the discussion:
http://lists.pgfoundry.org/pipermail/pgsqlrpms-hackers/2005-April/000197.html
-
53 matches
Mail list logo
