Thanks a lot, this helped me with the messages. I thought, I would only have to
define a operator class that fullfills at least the equals strategy. I didn't
know, that I would have to provide a full btree operator class.
Best regards
Carsten Kropf
Am 03.05.2010 um 15:56 schrieb Tom
still reports the same errors after having set up
the btree operator class.
How can I solve this issue?
Best regards
Carsten Kropf
of data items?
Best regards
Carsten Kropf
. However, it does not feel so right, to
return the OID for the type I want to use, using a query. I hope, that there is
some predefined function that I haven't found yet to determine the OID of some
type (or relation etc).
Best regards,
Carsten Kropf
--
Sent via pgsql-general mailing list
(const char *typname)
which does indeed do the lookup of my particular type in the cache and system
catalog tables. Thanks a lot for the hint!
Best regards
Carsten Kropf
Am 22.03.2010 um 13:18 schrieb Tom Lane:
Carsten Kropf ckro...@fh-hof.de writes:
I wanted to ask, if there is a method
Oh, thanks, that's right, I see that this function I used before, searches only
in the currently used schema. The usage of parseTypeString is comparable easy,
as well, so based on your hints, I will probably use this function.
Best regards
Carsten Kropf
Am 22.03.2010 um 16:23 schrieb Tom
was testing in main memory
in some outstanding project, before).
Thanks in advance.
Best regards
Carsten Kropf
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
and will be deployed to postgres lib dir whenever you call install
on the makefile.
Best regards
Carsten Kropf
Am 17.03.2010 um 19:27 schrieb Stuart McGraw:
Hello all,
I know this is a very elementary question, but my excuse
is I have not programmed in C or written makefiles for
15
the
first option, but it does not seem to have good results based on the waste of
space. Could anyone please give me some help according to this issue?
Best regards
Carsten Kropf
according to this issue.
Thanks in advance
Best regards
Carsten Kropf
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
don't know exactly if it is really necessary (and,
as I already mentioned, how this would be possible).
Best regards,
Carsten Kropf
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
of the code and adopted it to my wishes. So,
now, I am totally confused how to set up a page properly without knowing how to
put data in using XLog components. Could anybody please give me a hint how to
achieve this?
Am I able to use the XLog stuff at all?
Best regards
Carsten Kropf
Am
Thanks a lot so far, got it working with the cast. Probably the documentation
about create type where the type modifiers are described should be extended in
order to find that.
Thanks and regards
Carsten Kropf
Am 18.02.2010 um 16:46 schrieb Tom Lane:
Yeb Havinga yebhavi...@gmail.com
column. How can I
achieve this/What do I have to do to get it to work?
Best regards
Carsten Kropf
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Carsten Kropf
Am 11.02.2010 um 16:39 schrieb Tom Lane:
Carsten Kropf ckro...@fh-hof.de writes:
Thanks a lot so far. I adopted my structures and am now storing two fields
(v_len_ and dimensions) and the storage is now working properly. If I now
would try to combine two of these points
with my actual work, after that.
Thank you in advance
Best regards
Carsten Kropf
regards
Carsten Kropf
Am 10.02.2010 um 11:39 schrieb Yeb Havinga:
Carsten Kropf wrote:
The usage of static types with fixed length was actually no problem for me,
so I proceeded to variable length types.
I created an n-dimensional point structure called PointND that contains a
field
Carsten Kropf
Am 10.02.2010 um 12:04 schrieb Yeb Havinga:
Carsten Kropf wrote:
Actually, I thought, I did this using the int32 variable called dimension
which should be exactly this field.
yes.
in = (PointND *) palloc(sizeof(float8) * dimensions + VARHDRSZ);
SET_VARSIZE(in, dimensions
, it is, in
fact, n-dimensional. So my problems are solved here. Btw I could manage to get
my own point to be saved in the database using your hints, thanks for this.
regards
Carsten Kropf
Am 10.02.2010 um 12:20 schrieb Yeb Havinga:
Carsten Kropf wrote:
Oh, I see, does the VARSIZE length
not look at the
right places until now). How would one do this?
Thanks in advance
regards
Carsten Kropf
Am 10.02.2010 um 12:20 schrieb Yeb Havinga:
Carsten Kropf wrote:
Oh, I see, does the VARSIZE length field have to be the total number of
bytes occupied (including VARHDRSZ
20 matches
Mail list logo
