Scott Marlowe wrote:
On Tue, Apr 7, 2009 at 7:12 PM, Kenneth Tilton wrote:
Scott Marlowe wrote:
You can use a different method if you need a table available to the
same session. Create a schema based on the session id, and put your
temp tables there, only don't call them temp tables. You'
On Tue, Apr 7, 2009 at 7:12 PM, Kenneth Tilton wrote:
>
>
> Scott Marlowe wrote:
>>
>> You can use a different method if you need a table available to the
>> same session. Create a schema based on the session id, and put your
>> temp tables there, only don't call them temp tables. You'll either
Scott Marlowe wrote:
You can use a different method if you need a table available to the
same session. Create a schema based on the session id, and put your
temp tables there, only don't call them temp tables. You'll either
need to make sure you always clean up your temp schema your session
c
Hi Kenneth,
One concern I have with SSD drives is that the performance degrades over time.
If you were not familiar with this issue already, take a look at the following
article.
http://www.anandtech.com/storage/showdoc.aspx?i=3531
It is not a huge problem and I have faith in Intel to come up
On Tue, Apr 7, 2009 at 5:05 PM, Kenneth Tilton wrote:
>
>
> Greg Smith wrote:
>>
>> Temp tables can be great for simplifying your code into more logical
>> sections. When making a case for using them, make sure to point out that
>> using them more aggressively can cut down on the amount of indexi
Greg Smith wrote:
Temp tables can be great for simplifying your code into more logical
sections. When making a case for using them, make sure to point out
that using them more aggressively can cut down on the amount of indexing
you need on the big tables, which has positive implications in t
Tom Lane wrote:
Kenneth Tilton writes:
I am porting a datamining web app to postgres from a non-sql datastore
and plan to use temporary tables quite a bit, to manage collections the
user will be massaging interactively. They might search and find
anywhere from 50 to 50k items, then filter t
Temp tables can be great for simplifying your code into more logical
sections. When making a case for using them, make sure to point out that
using them more aggressively can cut down on the amount of indexing you
need on the big tables, which has positive implications in terms of
getting simp
Kenneth Tilton writes:
> I am porting a datamining web app to postgres from a non-sql datastore
> and plan to use temporary tables quite a bit, to manage collections the
> user will be massaging interactively. They might search and find
> anywhere from 50 to 50k items, then filter that, unfilte
Hi All,
I'm getting some problems with UTF8 and Pgsql for some days. In the 8.3
version these problems became worse.
In the new version,
=> select convert(f0601_desc, 'UTF8', 'LATIN1') from f0601;
gives: ERROR: ... convert(character varying, unknown, unknown) don't exists
and
=> select con
Oleg Bartunov wrote:
> contrib/test_parser - an example parser code.
Using that as a template, I seem to be on track to use the regexp.c
code to pick out statute cites from the text in my start function, and
recognize when I'm positioned on one in my getlexeme (GETTOKEN)
function, delegating ev
On Tue, Apr 7, 2009 at 3:11 PM, Kenneth Tilton wrote:
> I am porting a datamining web app to postgres from a non-sql datastore and
> plan to use temporary tables quite a bit, to manage collections the user
> will be massaging interactively. They might search and find anywhere from 50
> to 50k item
I am porting a datamining web app to postgres from a non-sql datastore
and plan to use temporary tables quite a bit, to manage collections the
user will be massaging interactively. They might search and find
anywhere from 50 to 50k items, then filter that, unfilter, sort, etc.
Currently I mana
Magnus Hagander wrote:
> I don't know that anybody does. We usually get a report a couple of
> minor versions in and fix it then, which backs that guess. It's also
> not tested by the buildfarm. So I think you can call it semi-
> maintained at best.
>
> So if you want to become the maintainer
On Tue, Apr 7, 2009 at 1:36 PM, Cha Yang wrote:
> Postgresql 8.2
> backend to a Java application with JDBC
>
>
> For whatever reason all of postgresql tables all filled up to 1 gig each
> Accessing Postgresql through either the application or PGadmin fails
When they get to 1gig they start a new s
On Tue, April 7, 2009 16:07, Tom Lane wrote:
>
> You might find it more useful to add some elog(LOG) statements to
> the trigger body.
>
Thank you again. I will go through section 44.2 tonight.
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrnemailto:b
"James B. Byrne" writes:
> I am poking in the dark here. What I want to do is to determine if
> the trigger is firing and whether the function works as intended.
> At the moment I am not seeing anything show up in the secondary
> table so I have done something wrong. Is there some way of gettin
Postgresql 8.2
backend to a Java application with JDBC
For whatever reason all of postgresql tables all filled up to 1 gig each
Accessing Postgresql through either the application or PGadmin fails
any ideas of how to get into Postgresql or a way to clean up these tables?
thanks
--
Sent v
On Tue, April 7, 2009 15:09, Tom Lane wrote:
>
> ALTER DATABASE foo SET log_min_messages = whatever;
>
> Note this will only affect subsequently-started sessions. Also,
> if memory serves, you have to be superuser to set this particular
> variable.
Thanks. Am I correct to infer from the output
Tom Lane wrote:
> "Kevin Grittner" writes:
>> Can I use a different set of dictionaries
>> for creating the tsquery than I did for the tsvector?
>
> Sure, as long as the tokens (normalized words) that they produce
> match up for words that you want to have match. Once the tokens
> come out, t
On Tue, 7 Apr 2009, Kevin Grittner wrote:
Oleg Bartunov wrote:
of course, you can build tsquery youself, but once your parser can
recognize your very own token 'xxx', it'd be much better to have
mapping xxx -> dict_xxx, where dict_xxx knows all semantics.
I probably just need to have that "A
"Kevin Grittner" writes:
> Can I use a different set of dictionaries
> for creating the tsquery than I did for the tsvector?
Sure, as long as the tokens (normalized words) that they produce match
up for words that you want to have match. Once the tokens come out,
they're just strings as far as
Oleg Bartunov wrote:
> of course, you can build tsquery youself, but once your parser can
> recognize your very own token 'xxx', it'd be much better to have
> mapping xxx -> dict_xxx, where dict_xxx knows all semantics.
I probably just need to have that "Aha!" moment, slap my forehead, and
move
"James B. Byrne" writes:
> I am testing the trigger function that I wrote. Is there a way to
> increase the logging detail level for just a single database
> instance?
ALTER DATABASE foo SET log_min_messages = whatever;
Note this will only affect subsequently-started sessions. Also,
if memory
Not in regards to logging detail, but that function in general...
I'm pretty new to postgres, so I could be totally wrong in this, but I think
this thread
http://archives.postgresql.org/pgsql-performance/2008-03/msg00204.php
may pertain if you see some performance degradation with that trigger.
Li
I am testing the trigger function that I wrote. Is there a way to
increase the logging detail level for just a single database
instance? The manual indicates not, but just in case I am
misreading things I am asking here?
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrn
On Tue, 7 Apr 2009, Kevin Grittner wrote:
If the document text contains '341.15(3)' I want to find it with a
search string of '341', '341.15', '341.15(3)' but not '341.15(3)(b)',
'341.1', or '15'. How do I handle that? Do I have to build my
tsquery values myself as text and cast to tsquery, or
Tom Lane wrote:
Tino Wildenhain writes:
I would not recommend to do this within the database. Thats typical
a job for your presentation layer.
... but having said that, I think the "money" datatype has a function
for this. Whether that's of any use to you I dunno; mo
On Apr 7, 2009, at 8:07 AM, Steve Crawford wrote:
In scenario 2, there were two options:
2a. Return zero-element array.
2b. Return array with single empty-string element.
My impression was that among the "change" options, 2b had the most
support (it is the most useful for the use-cases I've e
This is what I have come up with. Comments are welcomed.
CREATE OR REPLACE FUNCTION hll_pg_fn_ident_insert()
RETURNS TRIGGER AS $pg_fn$
-- ROW AFTER TRIGGER
-- trigger passes identifier_type, _value and _description
-- received as ARGV[0], ARGV[1] and ARGV[2]
Steve Crawford wrote:
Did I miss the exciting conclusion or did this drift silently off radar?
it was pretty well split between the options. tabled for another time.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgr
Did I miss the exciting conclusion or did this drift silently off radar?
I seem to recall three options:
1. Leave as is. Arguments: least effort, no backward compatibility
issues, since array_to_string evaluate both an array with single empty
string and an array with no elements to an empty st
=?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= writes:
> dumped db with 2 week version of pg_dumpall (yeah, I know, install
> tools first, etc, but that's 8.4).
> now trying to restore it from that backup with new psql, gives me that:
> ERROR: syntax error at or near "COLLATE"
> LINE 1: ...ATE = template0
Oleg Bartunov wrote:
> contrib/test_parser - an example parser code.
Thanks! Sorry I missed that.
-Kevin
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
Hi everyone, thanks in advance. I'm using Win XP and trying to install
PostgreSQL 8.3, i've read the DOCs and followed every step carefully,
everything seems to be right on the progress bar untill it stucks and
prompts: "Failed to run initdb: 1! Please see the logfile in
"blabla"\tmp\initdb.log
dumped db with 2 week version of pg_dumpall (yeah, I know, install
tools first, etc, but that's 8.4).
now trying to restore it from that backup with new psql, gives me that:
ERROR: syntax error at or near "COLLATE"
LINE 1: ...ATE = template0 OWNER = gjaskie ENCODING = 'UTF8' COLLATE = ...
ideas
Kevin,
contrib/test_parser - an example parser code.
On Mon, 6 Apr 2009, Kevin Grittner wrote:
Tom Lane wrote:
"Kevin Grittner" writes:
People are likely to search for statute cites, which tend to have a
hierarchical form.
I think what you need is a custom parser
I've just returned to
--- On Tue, 7/4/09, Albe Laurenz wrote:
> I can find no VARATT_SIZEP in the PostgreSQL 8.3 headers.
> Where did you get that from?
>
> Yours,
> Laurenz Albe
>
I think it's depreciated and he should be using SET_VARSIZE instead ...
--
Sent via pgsql-general mailing list (pgsql-general@
Today I postgres on one of our servers shutdown with exit code 128.
Postgresql 8.3.7 on Windows 2003 server.
It started up normally but this is the second occurance this week.
Below is a section of the log. A restart of the service returned
postgres to normal. Suggestions?
Thanks,
Roger
2009-0
SHARMILA JOTHIRAJAH wrote:
> I use this Oracle function(from AskTom -
> http://asktom.oracle.com/pls/asktom/f?p=100:11:0P11_QUESTION_ID:210612357425)
>
>
>
>
> SQL> create or replace type myTableType as table
> of varchar2 (255);
> 2 /
>
> Type created.
>
> ops$tk...@dev8i>
eehab hamzeh wrote:
> I am trying to build some functions using C language. these functions are
> mentioned in the postgresql documentation.
>
> the only function that are work are the one with int32 variable.
> the other function bring errors and are not working
> any body can give directions
>
David Kerr wrote:
> I'm having a heck of a time trying to track this down.
> Is it possible to retrive a large object from psql/pgbench?
>
> I don't want just the OID, i want the actual streamed data.
>
> I'm doing a timing comparison between bytea and lo's. So it'd
> be ideal if I can pull it wi
I don't know that anybody does. We usually get a report a couple of
minor versions in and fix it then, which backs that guess. It's also
not tested by the buildfarm. So I think you can call it semi-
maintained at best.
So if you want to become the maintainer and test/send patches at an
ear
43 matches
Mail list logo
