Ritesh Nadhani wrote on 01.11.2006 07:51:
We have a server where Postgresql is running without any problem with
postgres username and admin rights.
Interesting. On Windows, PG will *refuse* to run on an account with admin
rights.
---(end of broadcast)
Hello All
Me and my professor are planning to work upon machine learning in
postgresql over tsearch2. So I have some questions:
We have a server where Postgresql is running without any problem with
postgres username and admin rights. I have a user account in that
server. I plan to compile an
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Do you mean you actually find stuff based on text attributes in JPEG
> images and the like? I thought those were compressed ...
Typically not --- the design assumption is that the text size wouldn't
amount to anything anyway compared to the image data,
>> We are not storing bytea, a customer is. We are trying to work around
>> customer requirements. The data that is being stored is not always text,
>> sometimes it is binary (a flash file or jpeg). We are using escaped text
>> to be able to search the string contents of that file .
>
> Hmm, have
Carlos Moreno <[EMAIL PROTECTED]> writes:
> Why is it that the database
> cluster is resrticted to a single locale (or single set of locales) instead
> of being configurable on a per-database basis?
Because we depend on libc's locale support, which (on many platforms)
isn't designed to switch betw
Joshua D. Drake wrote:
> Alvaro Herrera wrote:
> > Darcy Buskermolen wrote:
> >> On October 31, 2006 08:53 am, Teodor Sigaev wrote:
> The problem as I remember it is pg_tgrm not tsearch2 directly, I've sent
> a self contained test case directly to Teodor which shows the error.
>
>
I hesitate to mention it, since it's retrograde, uses OIDS, may not handle your
locale/encoding correctly, may not scale well for what you need etc., etc.
But we've used fti (in the contrib package) to do fast searches for any bit of
text in people's names ... we didn't go with tesearch2 because
"Tomi NA" <[EMAIL PROTECTED]> writes:
> 2006/10/31, Albe Laurenz <[EMAIL PROTECTED]>:
>> psql -h host -p port -d database -U user It's a good enough solution in most cases, but when the rowcount
> starts to skyrocket, it simply doesn't seem to cut it (at least I
> couldn't make it to).
It certain
Hello,
I am teaching yet another PostgreSQL class this week. I have limited
availability for those who are trying to reach me. I apologize if my
replies seem staggered and tardy.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667
Alvaro Herrera wrote:
> Darcy Buskermolen wrote:
>> On October 31, 2006 08:53 am, Teodor Sigaev wrote:
The problem as I remember it is pg_tgrm not tsearch2 directly, I've sent
a self contained test case directly to Teodor which shows the error.
'ERROR: index row requires 8792
Ray Stell wrote:
> I was interested in going down that path. This thread seems to be sparc
> oriented. How about on opteron? Will pg work on solaris10 without too
> much stress?
PostgreSQL will work wonderfully on Solaris10 Opteron.
Joshua D> Drake
>
>> isainfo -v
> 64-bit amd64 applicati
Teodor Sigaev wrote:
>> The problem as I remember it is pg_tgrm not tsearch2 directly, I've
>> sent a self contained test case directly to Teodor which shows the
>> error.
>> 'ERROR: index row requires 8792 bytes, maximum size is 8191'
> Uh, I see. But I'm really surprised why do you use pg_trgm
Hi,
Even though I *think* I have a fairly clear understanding of encoding
and locale principles, I'm somewhat unsure of how some of the tools
available with PostgreSQL apply (or rather, how should they be used).
1) The way I understand it, encoding (character set) and locale are two
different
On 10/31/06, Alan Hodgson <[EMAIL PROTECTED]> wrote:
On Tuesday 31 October 2006 11:48, "Merlin Moncure" <[EMAIL PROTECTED]>
wrote:
> you are talking about the gigabyte i-ram. in the database world, you
> can achieve same thing (actually better) by sticking those ram sticks
> directly on the moth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/31/06 17:17, Tomi NA wrote:
> 2006/10/31, Albe Laurenz <[EMAIL PROTECTED]>:
[snip]
> It's a good enough solution in most cases, but when the rowcount
> starts to skyrocket, it simply doesn't seem to cut it (at least I
> couldn't make it to). To l
2006/10/31, Albe Laurenz <[EMAIL PROTECTED]>:
> I have a little problem. I have an .sql file ( db dump )
> and i want to import it to postgres on linux.
>
> Does anyone know how i can do it?
You feed it to the command line interface psql.
Example:
psql -h host -p port -d database -U user
It
Hi list,
Le mardi 31 octobre 2006 20:00, Geoffrey a écrit :
> I have not had any success in duplicating the failure on my development
> environment. I suspect it's because I can't generate the volume of
> users. The production system could well have 150-200 users at one time
> and we get a core
Thanks to all who replied.
The reason I wanted to go 64-bit on our Fujitsu sparc-alikes was that our
sysadmins switched to 64-bit Perl as part of the standard package, and that
broke our DBD::Pg interface. With no warning, we started getting a message
about Pg.so, "Wrong ELF Class: ELFCLASS32
As I understand resier4, its features are irrelevant if your filesystem
will mostly be holding postgres data.
On Tue, 31 Oct 2006, km wrote:
Hi all,
Is anyone up with database features in reiserfs (reiser4) with postgresql 8.x?
regards,
KM
---(end of broadcast)-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/31/06 13:48, Merlin Moncure wrote:
> On 10/31/06, Adam <[EMAIL PROTECTED]> wrote:
>>
>>
>> I recently saw a Hard Disk Drive that is really 4GB of RAM with and SATA
>> 1.5Gb/s serial interface. It's basically a hard disk drive that uses
>> RAM.
>
I'd like to create a trigger function whose use can extend to multiple
tables by employing the special variables available (e.g., TG_RELNAME).
Below is a simple version of such a function that ought to prevent
insertion of greater than 4 total records in the table that calls it.
I'm not sure that I
On Tue, Oct 31, 2006 at 10:43:55AM -0700, [EMAIL PROTECTED] wrote:
> How widespread is the use of PostgreSQL on Solaris? I am beginning
Well, one of the core members (Josh Berkus) actually works for Sun,
and Sun is officially supporting PostgreSQL in some capacity.
Moreover, I ran our Postgres
On Tuesday 31 October 2006 11:48, "Merlin Moncure" <[EMAIL PROTECTED]>
wrote:
> you are talking about the gigabyte i-ram. in the database world, you
> can achieve same thing (actually better) by sticking those ram sticks
> directly on the motherboard assuming you are in a 64 bit environment
> and
On 10/31/06, Adam <[EMAIL PROTECTED]> wrote:
I recently saw a Hard Disk Drive that is really 4GB of RAM with and SATA
1.5Gb/s serial interface. It's basically a hard disk drive that uses RAM.
It also has a battery backup, so if you loose power, you don't loose your
data.
Has anyone tried usin
Darcy Buskermolen wrote:
> On October 31, 2006 08:53 am, Teodor Sigaev wrote:
> > > The problem as I remember it is pg_tgrm not tsearch2 directly, I've sent
> > > a self contained test case directly to Teodor which shows the error.
> > >
> > > 'ERROR: index row requires 8792 bytes, maximum size
Alvaro Herrera wrote:
I'm not 100% sure what you are saying here, but if it is what I believe,
then you didn't copy the newly compiled executable into the production
machine; that won't work. You need to use a debug-enabled executable
both to produce the core file, and to pass to GDB for inspec
I recently saw a Hard Disk Drive that is really 4GB
of RAM with and SATA 1.5Gb/s serial interface. It's basically a hard disk
drive that uses RAM. It also has a battery backup, so if you loose power,
you don't loose your data.
Has anyone tried using this, and if so was there a
noticeable
Ray Stell <[EMAIL PROTECTED]> writes:
> I was interested in going down that path. This thread seems to be sparc
> oriented. How about on opteron? Will pg work on solaris10 without too
> much stress?
It seems like most of the questions in this thread could be answered by
perusing the latest vers
On October 31, 2006 08:53 am, Teodor Sigaev wrote:
> > The problem as I remember it is pg_tgrm not tsearch2 directly, I've sent
> > a self contained test case directly to Teodor which shows the error.
> >
> > 'ERROR: index row requires 8792 bytes, maximum size is 8191'
>
> Uh, I see. But I'm rea
Geoffrey wrote:
> Alvaro Herrera wrote:
> >Geoffrey wrote:
> >>It appears that upgrading to 7.4.13 helped the problem we were having
> >>with the postgres process terminating. We still are having the problem,
> >>but it does appear to be different, based on the output of backtraces.
> >>The cor
On Oct 31, 2006, at 9:43 AM, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> wrote:
How widespread is the use of PostgreSQL on Solaris? I am beginning
to sense that community support is not currently very strong on
this platform, and that pgsql may not be the best candidate for my
current project
Alvaro Herrera wrote:
Geoffrey wrote:
It appears that upgrading to 7.4.13 helped the problem we were having
with the postgres process terminating. We still are having the problem,
but it does appear to be different, based on the output of backtraces.
The core files are much larger and there d
I was interested in going down that path. This thread seems to be sparc
oriented. How about on opteron? Will pg work on solaris10 without too
much stress?
> isainfo -v
64-bit amd64 applications
sse3 sse2 sse fxsr amd_3dnowx amd_3dnow amd_mmx mmx cmov amd_sysc cx8
tsc fpu
32-bit
Geoffrey wrote:
> It appears that upgrading to 7.4.13 helped the problem we were having
> with the postgres process terminating. We still are having the problem,
> but it does appear to be different, based on the output of backtraces.
> The core files are much larger and there does seem to be a
Hi,
On Tue, 2006-10-31 at 09:31 -0800, Richard Broersma Jr wrote:
> I heard that reiser4 is not yet stable. And that there is a chance
> that it wont be since its author is in detention.
Here are the links:
http://linux.slashdot.org/linux/06/10/15/0057203.shtml
http://yro.slashdot.org/yro/06/1
Hi.
Is it possible to limit number of left join rows that match condition to
1? I don't want to have hits from first table multiplied when more then
1 row matches on left join condition.
Thank you
Jure
---(end of broadcast)---
TIP 6: explain an
Hi Tom
Richard Huxton wrote:
Tim Tassonis wrote:
Hi Tom
Tom Lane wrote:
Tim Tassonis <[EMAIL PROTECTED]> writes:
The strange thing is, even with loglevel debug5, I don't get any log
message indicating that postgres is even trying to call the command.
Then it isn't, because there are defini
> Is anyone up with database features in reiserfs (reiser4) with postgresql
> 8.x?
I heard that reiser4 is not yet stable. And that there is a chance that it
wont be since its
author is in detention. Most of the recommendations that I've seen are to use
good-old-reliable
EXT3 which keeps you
Hi all,
Is anyone up with database features in reiserfs (reiser4) with postgresql 8.x?
regards,
KM
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's
Jure Ložar <[EMAIL PROTECTED]> schrieb:
> Hi.
>
> Is it possible to limit number of left join rows that match condition to 1?
> I don't want to have hits from first table multiplied when more then 1 row
> matches on left join condition.
I'm not sure if i understand you correctly, but perhaps t
On October 31, 2006 06:42 am, Joshua D. Drake wrote:
> Teodor Sigaev wrote:
> >> The problem I am after is the 8k index size issue. It is very easy to
> >> get a GIST index (especially when using tsearch2) that is larger than
> >> that.
The problem as I remember it is pg_tgrm not tsearch2 directl
Tim Tassonis wrote:
Hi Tom
Tom Lane wrote:
Tim Tassonis <[EMAIL PROTECTED]> writes:
The strange thing is, even with loglevel debug5, I don't get any log
message indicating that postgres is even trying to call the command.
Then it isn't, because there are definitely log messages, which were
s
Hi Tom
Tom Lane wrote:
Tim Tassonis <[EMAIL PROTECTED]> writes:
The strange thing is, even with loglevel debug5, I don't get any log
message indicating that postgres is even trying to call the command.
Then it isn't, because there are definitely log messages, which were
specifically put there
Teodor Sigaev wrote:
>> The problem I am after is the 8k index size issue. It is very easy to
>> get a GIST index (especially when using tsearch2) that is larger than
>> that.
> Hmm, tsearch2 GIST index is specially designed for support huge index
> entry:
> first, every lexemes in tsvectore are t
How widespread is the use of PostgreSQL on Solaris? I am beginning to sense
that community support is not currently very strong on this platform, and that
pgsql may not be the best candidate for my current project -- installing LXR on
a 64-bit Solaris system.
I had to do a lot of web searching
Antonios Katsikadamos wrote:
Hi all I am a new linux and postgres user and i don't
know how i canconfigure the postgres on suse linux in
order to make it run.
I would be thankful for any tip.
Antonios,
Finally I have installed successfully PostgreSQL 8.1.5 under a clean
OpenSUSE 10.0 64-bit
Tim Tassonis wrote:
Hi Tom
Richard Huxton wrote:
Tim Tassonis wrote:
Hi Tom
Tom Lane wrote:
Tim Tassonis <[EMAIL PROTECTED]> writes:
The strange thing is, even with loglevel debug5, I don't get any
log message indicating that postgres is even trying to call the
command.
Then it isn't, be
It appears that upgrading to 7.4.13 helped the problem we were having
with the postgres process terminating. We still are having the problem,
but it does appear to be different, based on the output of backtraces.
The core files are much larger and there does seem to be a common thread
amongst
The problem as I remember it is pg_tgrm not tsearch2 directly, I've sent a
self contained test case directly to Teodor which shows the error.
'ERROR: index row requires 8792 bytes, maximum size is 8191'
Uh, I see. But I'm really surprised why do you use pg_trgm on big text? pg_trgm
is desig
Tim Tassonis <[EMAIL PROTECTED]> writes:
> The strange thing is, even with loglevel debug5, I don't get any log
> message indicating that postgres is even trying to call the command.
Then it isn't, because there are definitely log messages, which were
specifically put there for the purpose of rec
Richard Huxton wrote:
Tim Tassonis wrote:
We use version 8.1.3 and the following archive_coomand:
archive_command = 'copy %p d:\\backup\\logs\%f'
^^^
Could the lack of a double-backslash be causing the problem?
Sorry, that was a problem on my quot
> I have a little problem. I have an .sql file ( db dump )
> and i want to import it to postgres on linux.
>
> Does anyone know how i can do it?
You feed it to the command line interface psql.
Example:
psql -h host -p port -d database -U user http://www.postgresql.org/docs/faq
Hi all, I have a little problem. I have an .sql file ( db dump ) and i want to import it to postgres on linux. Does anyone know how i can do it? thnx a lot mates
We have the perfect Group for you. Check out the handy changes to Yahoo! Groups.
53 matches
Mail list logo
