've to use
@@@
Um, could you clarify that? I know the general differences between gist
and gin, but not how it affects weighted searches...
Kind regards,
Mikkel H??gh
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
wo-letter codes (en, da, pt, etc.) and as far as I can
understand the PostgreSQL documentation, tsearch expects the full
language name (english, danish, portuguese), so to use it in queries
without having to do too much magic would require me to store the full
name right there in the table, o
can I fix this problem..
You can have the server start automatically upon boot.
Beyond that, you have no need to 'su postgres'. You can use psql as any
user on the machine (provided the permissions are all set correctly).
Can you be more specific about what the 'problem' is?
&
On Tue, Jul 10, 2001 at 11:30:05AM +0800, some SMTP stream spewed forth:
> Would appreciate a lot if anyone could tell me if there is any
> disadvantage/performance issue in using PostgeSQL on windows.
I know of no disadvantages that are not a direct result of Windows.
Such things as the shared
e data after
>upgrade?!!!
>
> pls help. Thanks
It is my understanding that no dump/restore is necessary for minor
version upgrades (e.g. .2 to .3). You should be fine, but don't take my
word for it.
gh
--
> What, no one sings along with Ricky Martin anymore?
My kid sister does (but
t /feels/ better. Furthermore, a
stronger DBMS is more likely to serve your needs in the future.
> Speed is what I am lookin for
In what type of situation are you planning to use this setup?
gh
(Not a very strong argument, but MSSQL /is/ made by Microsoft, afterall...)
-
not know what later releases are
going to look like. It should still be better than Linux, but you
shouldn't have to learn something new if everything sucks anyway.
(Of course, the fine hackers behind PostgreSQL ensure that it runs well on
just about anything, so performance should not be an
4.0-MSSQL to Linux-Postgresql.
>
> What do you all think ? Should I change ?
Yes.
gh
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
post was uninformed...yet RedHat is all of Linux
now?
If you are going to refute a statement, please at least have the decency
to READ it.
Can we end this?
gh
---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregist
ective creates a
unique not null column, whereas a unique column can be null. In this
instance, your columns are already not null, so, as Eric responded, it is
basically the same thing.
gh
> --
> Eric G. Miller <[EMAIL PROTECTED]>
>
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://www.postgresql.org/search.mpl
would be even remotely useful.
Is it really that difficult to remove a comma?
If it works now for *all* users of PostgreSQL, why should we change it?
gh
>
> I suppose it isn't a major problem, but enforcing strict grammar
> helps to show up inadvertent errors. Suppose I ha
ther we can worry about what BC is
supposed to mean. I challenge you to stop them from killing each other.
gh
> "Common Era". Throughout history BC, when associated with a date, has
> always stood for "Before Christ", and it always will. I challenge the
> author/editor t
On Tue, Apr 10, 2001 at 09:27:50PM +0200, some SMTP stream spewed forth:
> Is there a way to perform a point in time restore with postgresql ?
>
Nope, not yet anyway, to the best of my knowledge.
dan
> /Claes
>
>
>
> ---(end of broadcast)---
On Fri, Apr 06, 2001 at 09:11:38PM -0400, some SMTP stream spewed forth:
> I didn't get a response on my message, so I thought I would try again.
>
> 1. A large object has the data type OID. What then, is the data type of the
> instance object identifier? Is it an int4?
>
I believe it is of
Has anybodys grabbed development of a standard deviation/variance
calculation function?
If not, I am interested in tacking it on my todo list.
What would be involved?
That is, should it be written in C or in PL/PgSQL, or what?
(I imagine that C would be fastest, no?)
Cheers,
dan
---
On Sun, Mar 04, 2001 at 05:22:46PM +, some SMTP stream spewed forth:
> Hi all,
>
> Is there any SQL statement to PostgreSQL that will allow me to insert rows
> with a specified value for the SERIAL value. I know this is not what you
> want to do normally, but I'm trying to provide a kind of
On Thu, Mar 01, 2001 at 10:21:53AM -0500, some SMTP stream spewed forth:
> hello
>
> i want to find the differences between two database schemas...is there a
> function for this or do i just pg_dump both of them and do a diff in unix?
As far as I know, such a function (or program/script) does n
annot find it.
I thank you for your assistance.
gh
If it helps, here is the `explain` output:
NOTICE: QUERY PLAN:
Unique (cost=337.77..338.51 rows=7 width=44)
-> Sort (cost=337.77..337.77 rows=74 width=44)
-> Append (cost=0.00..335.47 rows=74 width=44)
->
On Wed, Jan 31, 2001 at 02:58:23PM -0500, some SMTP stream spewed forth:
> postgres support for pl/VB? :)
Well, the most important, of course, would be pl/COBOL!!!
gh
>
> Adam Lang
> Systems Engineer
> Rutgers Casualty Insurance Company
> http://www.rutgersinsurance.co
abase hash the hash
might actually work reasonably well. But not really.
By hashing it, you increase the number of members in the set of
keys that the database would consider "valid" (or that would be
such that would allow access) provided that the database hashes the hash.
Otherwise, you are back in the same f'mess. Which you pretty much are
anyway, as the "key" simply becomes the hash of the "real" "password" if
you bypass the frontend. A someone else mentioned, a shared secret setup
would go far to avoiding a problem like this. But, if you cannot trust
your connection for a shared secret setup, you have a bigger problem. ;-)
Have fun.
gh
>
> -Ron-
q;
> END;
> ' LANGUAGE 'plpgsql';
>
> -- implicit BEGIN;
> SELECT new_tests();
> -- implicit COMMIT;
> SELECT new_tests();
> SELECT new_tests();
>
> SELECT * FROM test1;
> SELECT * FROM test2;
>
> DELETE FROM test1 WHERE id = 1; -- t
Is something like the following allowed (or is not a Bad Idea)?
table1
-+-
id1 |serial primary key
col2 |int references table2(id2)
table2
-+-
id2 |serial primary key
col2 |int references table1(id1)
Obviously,
dex.
>
> My feeling sais, that 0 and NOT NULL should be a lot more faster, but
> perhaps it's not true?
If your SELECT uses the index on the NOT NULL column, then yes, the
indexed 0 should be faster. I think it takes less space as well.(?)
gh
>
>
> bye
> Alvar
>
developers as well as to the community.
We have a Good Thing.
gh
and failed. I
>don't know if this was just my stupidity and I should have know to delete these
>triggers or if this is a bug. Either way, I learned something new.
Other than that, why would the connection die?
It seems like an error would be better.
gh
>
> Thanks,
> Darrin
7;ve not experienced it to really know first
> hand. Thanks for the input.
>
> If a couple more people would just say the same thing - I could rest easy
> about moving forward on this. :)
Well, based on my experience at this point, Tom Lane's
comments/suggestions are worth those of several people. Consider it as if
I have said the same as he. ;-)
gh
>
that's why we are here, eh?
I hope that I have been (at least somewhat) helpful.
"'Aaarghh!' went Ford Prefect...", The Hitchhiker's Guide to
the Galaxy, Douglas Adams
gh
>
> --
> Jean-Christophe Boggio
> [EMAIL PROTECTED]
> Independant Consultant and Developer
> Delphi, Linux, Oracle, Perl
>
>
or some such?
\end{Devils Advoate}
do
{
sleep();
} while(tired())
gh
>
> one of our brethren has seen it be reset back to 450 at least twice so far
> ...
>
> I'm curious ... is this survey supposed to have any accuracy to it, or are
> the results fixe
some ppl, but don't really want to
> > install PgSQL? *raised eyebrow*
>
> The counter was reset to 450ish twice just while I've been watching.
> They mustn't be too keen on installing it...
Er, do they not suppose that people are watching them do these things?
gh
On Sun, Dec 03, 2000 at 04:14:48PM -0600, some SMTP stream spewed forth:
> looks like it backfired...they've reset the graph
Sheesh! Apparently *everybody* wants a recount.
gh
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL
ou are using '\d' in psql.
Add the '-E' option when you start psql and it will show the specific
commands that it uses to expand things like '\d'.
It is a bit messy, though.
gh
>
> thanks
> adam
>
not the webserver that does the actual connection to the database
rather than any module such as PHP?
Thanks.
gh
On Sun, Nov 26, 2000 at 10:24:28PM -0500, some SMTP stream spewed forth:
> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > Probably we really need here is a kind of ping tool for PostgreSQL,
*snip*
> (BTW, a short-term answer for grasshacker is not to use -w in his
> pg_ctl start script ...)
Heh,
On Sun, Nov 26, 2000 at 10:53:24PM +0100, some SMTP stream spewed forth:
> GH writes:
>
> > Either way, any suggestions?
>
> Personally, I don't trust pg_ctl farther than I can throw it. Consider
> not using it.
Heh, I certainly have...but defaults that lock up
sleep 1
fi
done
$ECHO "done."
fi
That damn loop has brought down two of my servers already.
It seems like a bloody bad idea to have such a thing in a startup script,
eh? Or am I maybe just not supposed to set a password for pgsql?
Either way, any suggestions?
gh
riginal"
record. Likely, your PHP setup has magic_quotes_runtime (or
magic_quotes_gpc) set to On. This would cause PHP to "addslashes()" to
the data gathered from the db (also true for forms, etc).
Make sense?
You can use get_magic_quotes_runtime or get_magic_quotes_gpc to retrieve
the current setting of the two options.
http://www.php.net/manual/configuration.php#ini.magic-quotes-gpc
gives a nice summary.
cheers.
gh
>
uence]
but, how do I select the set of numbers that make up the sequence?
Is there a better/cleaner/easier way of getting the end result?
Postgres 7.0.2 (should be running .3, *sigh*)
FreeBSD 4.1-RELEASE
PHP 4.0.3pl1
Thanks fellas (and ladies, if applicable).
gh
On Fri, Nov 24, 2000 at 08:35:34AM +0300, some SMTP stream spewed forth:
> On Mon, Nov 20, 2000 at 12:44:20PM +0800, BaiJie wrote:
> > I KNOW THERE IS A OID FIELD ,BUT IT 'S WIRED , NOT A INTEGER INDEX FROM I TO
> > CURRENT ROW NUMBER!! HOW CAN I GET THE TRUE ROW NUMBER IN POSTGRESQL!!
> At first
On Wed, Nov 22, 2000 at 07:51:50PM -0500, some SMTP stream spewed forth:
> GH <[EMAIL PROTECTED]> writes:
> > The owner of the database and table may run rampant on any tables that
> > have *no* permissions granted. On tables with permissions granted to
> > anyone o
refused to anyone except the
owner. Er, that is supposed to happen, correct?
Thanks.
gh
he pgsql directory.
That sounds correct..
G'luck and
cheers
gh
41 matches
Mail list logo
