On Wed, Oct 18, 2000 at 03:11:12PM -0700, Nate Lawson wrote:
> In MySQL, I can get a hash of a VARCHAR by using the PASSWORD('') call. I
> know for DB admin there is pg_passwd, but is there a function interface so
> that I can get password hashes of arbitrary strings in SQL? (Note that I
> mean c
> SELECT FROM WHERE table1.field (+) = table2.field;
>
> This will return all appropriate rows in table1, even if no
> corresponding value exists in table2 (it'll list an empty value for that
> column in the output tuples if no value exists).
In order to do that you should put the (+) operator
Hi again, thanks for all your responses, now that I've taken a better look
at my problem, let me rephrase my question
I'm moving an app. from oracle to postgres, and I'm having problems with
the data type "time" I was able to format oracle's datatype "date" to
anything I'd like using to_char func
>Can someone point me at any resources on the web that can help with such a
>transformation? I have a series of tables I want to convert. Thanks.
>
>Oh, and I'm not on the list so can you email direct! :)
I don't know MySQL, but I've converted tables from mSQL to pgsql by
just using the dump t
Thanks! vacuum did get rid of those messages. The last time
import/rebuild worked it took over 2hrs, now it's down to 30min!
But the original problem ...
I'm finally starting to get some log entries, but they are in
/var/pgsql/log instead of /var/pgsql/postmaster.log - any ideas? probably
an
I'm also interested, so could you post to the list?
Thanx,
Mike Diehl,
Network Monitoring Tool Devl.
284-3137
[EMAIL PROTECTED]
> -Original Message-
> From: David Reid [mailto:[EMAIL PROTECTED]]
> Sent: October 19, 2000 5:31 AM
> To: [EMAIL PROTECTED]
> Subject: [GENERAL] MySQL -> pgsql
There is an artifical way to do the outer join in PostgreSQL... It
involves using UNION and NOT IN... see :
http://www.postgresql.org/docs/aw_pgsql_book/node305.html
Hope this helps...
-jag
--
"She who is wanting me,
Whose touch can make me cry,
I can only understand
By never asking her why.
I'm not sure about the standard, but I really like Oracle's notation for
foreign keys:
select a.item_number, b.group_code_description
from items a, group_codes b
where a.group_code = b.group_code (+);
Much better than
select a.item_number, b.group_code_descriptio
Tom Lane wrote:
>
> Philip Hallstrom <[EMAIL PROTECTED]> writes:
> > larger than the builtin limit for tuples. Is there anything I should be
> > aware of before changing the below value and recompiling?
>
> Only that it will force an initdb. Note the 32k limit, too.
>
> A trick you can use in
KuroiNeko wrote:
>
> Ray,
>
> > What am I doing wrong? Any ideas wold be helpful!
>
> Environment is dropped by cron. Either specify LD_LIBRARY_PATH in crontab
> explicitly, or add your PG libdir to /etc/ld.so.conf and rerun ldconfig.
>
Or do what I do in my cron scripts:
. ~/.bashrc ; myc
On Thu, Oct 19, 2000 at 04:24:54PM -0400, Joseph Shraibman wrote:
> Uh, why. Does TOAST do automatic compression? If people need to store
> huge blocks of text (like a DNA sequence) inline compression isn't just
> a hack to squeeze bigger text into a tuple.
Yes, TOAST does do automatic compress
> > A trick you can use in 7.0.* to squeeze out a little more space is
> > to declare your large text fields as "lztext" --- this invokes
> > inline compression, which might get you a factor of 2 or so on typical
> > mail messages. lztext will go away again in 7.1, since TOAST supersedes
> > it,
Ulf Mehlig <[EMAIL PROTECTED]> writes:
> NOTICE: PortalHeapMemoryFree: 0x0x40b139c8 not in alloc set!
> NOTICE: PortalHeapMemoryFree: 0x0x40b139c8 not in alloc set!
>
> select s_id,nummer,
> min(timest::time) as timest,
^
>
I don't think this will work in all cases. The index syntax is different
between mysql and psql. For example, I specify indexing in the create
clause under mysql; I use a separate statement to create an index under
psql. Am I missing something?
Thanx,
Mike Diehl,
Network Monitoring Tool Devl.
At 2:43 PM -0600 10/19/00, Diehl, Jeffrey wrote:
>I don't think this will work in all cases. The index syntax is different
>between mysql and psql. For example, I specify indexing in the create
>clause under mysql; I use a separate statement to create an index under
>psql. Am I missing somethin
Joseph Shraibman <[EMAIL PROTECTED]> writes:
>> A trick you can use in 7.0.* to squeeze out a little more space is
>> to declare your large text fields as "lztext" --- this invokes
>> inline compression, which might get you a factor of 2 or so on typical
>> mail messages. lztext will go away agai
The database I am hoping to migrate has a few tables with around 50K
records. These databases get updated every hour, 24/7. I don't think I can
do the migration with a text editor. So, I'm still looking for some other
method if it exists.
Conversion tools? Na, that's just a small part of what
On Thu, Oct 19, 2000 at 03:18:50PM -0600, Diehl, Jeffrey wrote:
> The database I am hoping to migrate has a few tables with around 50K
> records. These databases get updated every hour, 24/7. I don't think I can
> do the migration with a text editor. So, I'm still looking for some other
> metho
"Edmar Wiggers" <[EMAIL PROTECTED]> writes:
> I'm not sure about the standard, but I really like Oracle's notation for
> foreign keys:
> select a.item_number, b.group_code_description
> from items a, group_codes b
> where a.group_code = b.group_code (+);
I beg to differ --- IMH
Excuse my ignorance but I have browsed TODO list and haven't found
anything...
What is WAL?
Greets.
David
> Conversion tools? Na, that's just a small part of what I do.
Since it's a network monitor, chances are you're not using exotic
datatypes incompatible, or non-existant in PGSQL? If so, the fastest way
would be to get a `dump' schema + data script from MySQL and adjust it with
sed or
Tom Lane wrote:
>
> Joseph Shraibman <[EMAIL PROTECTED]> writes:
> >> A trick you can use in 7.0.* to squeeze out a little more space is
> >> to declare your large text fields as "lztext" --- this invokes
> >> inline compression, which might get you a factor of 2 or so on typical
> >> mail messag
Steve Wolfe wrote:
>
> > > A trick you can use in 7.0.* to squeeze out a little more space is
> > > to declare your large text fields as "lztext" --- this invokes
> > > inline compression, which might get you a factor of 2 or so on typical
> > > mail messages. lztext will go away again in 7.1, s
But remember, that mysql doesn't have rules, triggers and such. Moving the
data is all I need to do. I guess I could write a tool to select from mysql
and insert into psql... I was hoping someone else had already done it. ;^)
Mike Diehl,
Network Monitoring Tool Devl.
284-3137
[EMAIL PROTECTED]
Yup. Seems like that is what I need to do.
Thanx,
Mike Diehl,
Network Monitoring Tool Devl.
284-3137
[EMAIL PROTECTED]
> -Original Message-
> From: Neil Conway [mailto:[EMAIL PROTECTED]]
> Sent: October 19, 2000 3:30 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [GENERAL] MySQL -> pgsql
>
Tom Lane wrote:
>
> "Edmar Wiggers" <[EMAIL PROTECTED]> writes:
> > I'm not sure about the standard, but I really like Oracle's notation for
> > foreign keys:
>
> > select a.item_number, b.group_code_description
> > from items a, group_codes b
> > where a.group_code = b.group_c
> But remember, that mysql doesn't have rules, triggers and such.
That's exactly what I mean when I suggest re-designing the schema from
scratch. Otherwise, you only get `a half of it.'
> I guess I could write a tool to select from mysql
> and insert into psql...
This can be easy, up to
> In some cases yes, in some no. Simple text should compress/decompress
> quickly and the cpu time wasted is made up for by less hardware access
> time and smaller db files. If you have a huge database the smaller db
> files could be critical.
Hmm... that doesn't seem quite right to me. Whe
DaVinci wrote:
>
> Excuse my ignorance but I have browsed TODO list and haven't found
> anything...
>
> What is WAL?
>
> Greets.
>
> David
Write Ahead Logging.
i.e. Whenever you do an UPDATE to postgres it is garunteed to be in the
log, and the
OK. Thanks to all who replied. Here are my first impressions...
- pgsql is fussier about names of columns than mysql. e.g. a column name of
position was rejected by pgsql but seems to be OK in mysql.
- PRIMARY_KEY() syntax is OK for pgsql (which was a relief)
- There seem to be a lot more type
After my last email, I added the rest of the rule actions. So the
relevant part of the schema now looks like this:
CREATE RULE update_msg_stats
AS ON INSERT TO messages DO (
UPDATE users SET num_posts = num_posts + 1
WHERE users.id = new.poster;
UPDATE threads SET
[stuff about why 7.1 isn't out and the 8K limit and TOAST AND WAL snipped]
> And do you really think that WAL is more important that TOAST? I
> imagine a good percentage of users bump up against the 8K limit and end
> up with corrupted data (like I did) but much fewer think that WAL is a
> criti
what is the best way to set-up keywords in tables and Queries? please post
examples!
I am worried about a field for each keyword
less
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane and I will be speaking at the Open Source Database Summit,
> > October 30 and 31, in San Jose, California.
>
> For anyone who's interested, copies of the slides for my presentations
> are up in PDF format at http://www.postgresql.org/osdn/i
34 matches
Mail list logo
