On 10/29/2005, "blackwater dev" <[EMAIL PROTECTED]> wrote:
>In MySQL, I can use the replace statement which either updates the
>data there or inserts it. Is there a comporable syntax to use in
>postgreSQL?
>
>I need to do an insert and don't want to have to worry about if the
>data is already th
am 29.10.2005, um 20:39:23 -0700 mailte Matthew Peter folgendes:
> Could someone help me and give me a basic example of
> how to write a similiar functional function to the one
> below that would use a dynamic table and update a
> column only if it held a value.
http://www.postgresql.org/docs/8.
Oh my god!
DB is pg 7.4.6 on linux
2005-10-27 05:55:55 WARNING: some databases have not been vacuumed in
2129225822 transactions
HINT: Better vacuum them within 18257825 transactions, or you may have
a wraparound failure.
2005-10-28 05:56:58 WARNING: some databases have not been vacu
On Sun, Oct 30, 2005 at 08:50:18AM +, John Sidney-Woollett wrote:
> Oh my god!
>
> DB is pg 7.4.6 on linux
Firstly, check pg_database, it should tell you which databases need to
be vacuumed. Any database you regularly vacuumed is fine so maybe the
corruption is in some other database you
On Fri, Oct 28, 2005 at 09:57:03PM -0400, blackwater dev wrote:
> In MySQL, I can use the replace statement which either updates the
> data there or inserts it. Is there a comporable syntax to use in
> postgreSQL?
Not really, but here's an example which doesn't have the brokenness of
MySQL's REPL
Martin, thanks for the feedback.
I had a look around and couldn't see any data loss (but wasn't really
sure where to start looking).
I decided to switch over to the slave which is now our live database.
the old master with the problem has already been re-inited (although I
have a cold backup
Am Sonntag, den 30.10.2005, 06:29 -0800 schrieb David Fetter:
> On Fri, Oct 28, 2005 at 09:57:03PM -0400, blackwater dev wrote:
> > In MySQL, I can use the replace statement which either updates the
> > data there or inserts it. Is there a comporable syntax to use in
> > postgreSQL?
>
> Not reall
On Sun, Oct 30, 2005 at 03:52:23PM +0100, Tino Wildenhain wrote:
> Am Sonntag, den 30.10.2005, 06:29 -0800 schrieb David Fetter:
> > On Fri, Oct 28, 2005 at 09:57:03PM -0400, blackwater dev wrote:
> > > In MySQL, I can use the replace statement which either updates
> > > the data there or inserts i
At 06:29 AM 10/30/2005 -0800, David Fetter wrote:
On Fri, Oct 28, 2005 at 09:57:03PM -0400, blackwater dev wrote:
> In MySQL, I can use the replace statement which either updates the
> data there or inserts it. Is there a comporable syntax to use in
> postgreSQL?
Not really, but here's an exam
John Sidney-Woollett <[EMAIL PROTECTED]> writes:
> I decided to switch over to the slave which is now our live database.
> the old master with the problem has already been re-inited (although I
> have a cold backup of the data dir), plus dump files that I can restore
> from.
You panicked much t
Hi there,
I have a problem when sorting records with:
SELECT * FROM table WHERE name LIKE 'Ö%'
I am running Postgres 8.02 with a database whose character encoding is
UNICODE.
The SQL Query
SELECT *
FROM member
WHERE name LIKE 'O%'
OR
name like 'Ö%'
ORDER BY
Hi Tom
You're not wrong about panicking! This is the worst Sunday I've had in a
while... No sunday lunch or time with the kids... :(
This database supports a (normally 24/7) website and we couldn't
tolerate any possibility of data corruption. I had to make a judgement
call on preventing any/
On Sun, Oct 30, 2005 at 11:47:41PM +0800, Lincoln Yeoh wrote:
> At 06:29 AM 10/30/2005 -0800, David Fetter wrote:
>
> >On Fri, Oct 28, 2005 at 09:57:03PM -0400, blackwater dev wrote:
> >> In MySQL, I can use the replace statement which either updates
> >> the data there or inserts it. Is there a
Nico Grubert <[EMAIL PROTECTED]> writes:
> I have a problem when sorting records with:
> SELECT * FROM table WHERE name LIKE 'Ö%'
> I am running Postgres 8.02 with a database whose character encoding is
> UNICODE.
... but what locale is it using? (See LC_COLLATE and LC_CTYPE.)
... but what locale is it using? (See LC_COLLATE and LC_CTYPE.)
Can I find out out these settings in "phpPgAdmin"?
Or can I use LC_COLLATE and LC_CTYPE in the SQL Query?
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ig
John Sidney-Woollett <[EMAIL PROTECTED]> writes:
> I can restore the file system backup of pgsql/data to another database
> server and then get the info from pg_database. Or I can import a dump
> file from 15 minutes before I re-inited the database...
Importing a dump will tell you nothing at al
Ah, I found it:
lc_collate: [EMAIL PROTECTED]
lc_ctype: [EMAIL PROTECTED]
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
OK, I restored the pgsql/data to another server and started up postgres
and this is what I got:
SELECT datname, age(datfrozenxid) FROM pg_database;
datname| age
--+-
mail_lxtreme | -2074187459
bp_live | 1079895636
template1| 1076578064
template0
John Sidney-Woollett <[EMAIL PROTECTED]> writes:
> OK, I restored the pgsql/data to another server and started up postgres
> and this is what I got:
> SELECT datname, age(datfrozenxid) FROM pg_database;
> datname| age
> --+-
> mail_lxtreme | -2074187459
>
http://www.oracle.com/technology/software/products/database/xe/index.html
http://news.zdnet.com/2100-3513_22-5920796.html
'Oracle intends to release a free version of its database, a reaction
to the growing competitive pressure from low-end open-source
databases.'
Your thoughts?
--
Best regards,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a php script to upgrade a database, and it works just fine when not in a
transaction, but it fails when I turn on a transaction.
I'm using:
fedora core 4
postgresql 8.0.3
php-pgsql-4.3.11
The error is:
[db_error: message="DB Error: unknown er
Hmm. I'm pretty sure that database mail_lxtreme was unused (no
connections/activity) - I didn't think that it would need to be vacuumed
at all...
Just out of curiousity would the wraparound error (for mail_lxtreme)
actually have affected data in bp_live?
Could I just have deleted mail_lxtrem
On Sat, Oct 29, 2005 at 05:56:41PM -0500, [EMAIL PROTECTED] wrote:
> I have a php script to upgrade a database, and it works just fine when not in
> a
> transaction, but it fails when I turn on a transaction.
When you start a transaction and you get an error, all subsequent
commands will be ignor
On Sun, Oct 30, 2005 at 06:41:45PM +, John Sidney-Woollett wrote:
> Hmm. I'm pretty sure that database mail_lxtreme was unused (no
> connections/activity) - I didn't think that it would need to be vacuumed
> at all...
A database that is never used still needs to be vacuumed. The only
excepti
Thanks I did read that when looking into EXECUTE,
which I'd rather not use. As I said, I would rather
not use plpgsql if possible.
All I want to do is 1) pass in some variables, 2)
reference them, and 3) have a working query which 4)
supports SELECTs, and lastly 5) isn't plpgsql but
pg_native sy
Nikolay Samokhvalov wrote:
> http://www.oracle.com/technology/software/products/database/xe/index.html
> http://news.zdnet.com/2100-3513_22-5920796.html
>
> 'Oracle intends to release a free version of its database, a reaction
> to the growing competitive pressure from low-end open-source
> databa
John Sidney-Woollett <[EMAIL PROTECTED]> writes:
> Just out of curiousity would the wraparound error (for mail_lxtreme)
> actually have affected data in bp_live?
> Could I just have deleted mail_lxtreme and then continued to use bp_live
> as though nothing had happened?
No, and yes, which is why
Martijn
Thanks for the answers/thoughts...
Vacuumuming the databases hammers the server so the vacuums are spread
out at different times during the night/morning. Plus template1 is
vacuumed once a week.
I guess I was unlucky to have missed the vacuum on that unused database
(due to my misun
Hi,
On Sun, 30 Oct 2005, Bruce Momjian wrote:
'Oracle intends to release a free version of its database, a reaction
to the growing competitive pressure from low-end open-source
databases.'
Your thoughts?
It probably has little impact on us. It is useful perhaps for developer
servers at exi
"Panic" - that's my middle name. ;)
Had I known how to identify the database at fault, and that it would
have had no effect on the other databases, then I would have handled
this episode differently.
In the event, things seem to be OK. Our old slave db is now acting as
master and the old mas
> 1. Windows XP
> 2. QUANTUM FIREBALLP LM20.5 (IDE drive)
> 3. Write caching is off in XP device manager
> 4. fsync is ON in Postgres 8
Coming late into the discussion, there is one more note I'd add to this
- if you're on windows and want to be extra secure, also set
wal_sync_method=fsync_writet
On Sat, 2005-10-29 at 09:10 -0600, Michael Fuhr wrote:
> On Fri, Oct 28, 2005 at 06:22:43PM -, [EMAIL PROTECTED] wrote:
> > This is postgresql 7.4
> > I am trying to check that postgres is updating a table.
> > I have a pretty large ascii table file (+- 210 Mb) which I am copying into
> > a
>
Nikolay Samokhvalov wrote:
> http://www.oracle.com/technology/software/products/database/xe/index.html
> http://news.zdnet.com/2100-3513_22-5920796.html
>
> 'Oracle intends to release a free version of its database, a reaction
> to the growing competitive pressure from low-end open-source
> databa
Hi,
I'm looking for some help in regards to letting Posresql use more
memory. It fails to start with this message:
shmat(id=65536) failed: Cannot allocate shared bufers
Max buffers I can start it with is 115200. Server has 4gig of RAM,
I've adjuted MAXDSIZ to 2.5Gigs. Here is other kernel settin
Vlad <[EMAIL PROTECTED]> writes:
> I'm looking for some help in regards to letting Posresql use more
> memory.
8.0 can't go past 2Gb of shared memory, and there is really no reason
to try because its performance will get worse not better with more than
about 5 shared buffers.
8.1 will relax t
After a couple of months of testing, and alot of bug reports (with fixes),
we are pleased to announce the first Release Candidate of PostgreSQL
8.1.0.
As with all pre-releases, but especially now that we are in the final
stretch, testing is paramount to a successful, and bug free, release.
Tom,
I understood your point on memory usage. Out of curiosity - 115200
buffers seems to be little less than 1 gig (I assume 1 buffer = 8k),
so I could not get any closer to 2gigs anyways
Is it practical experience that more than 5 buggers actually hurts
postgresql performance? Any ideas
Here are some apparent problems with MySQL 5.0:
- Concurrent ALTER TABLE
- Replicated Session Variables and Concurrent ALTER
TABLE
- BIT indexing that [doesn't] actually uses a BIT!
- SELECT * FROM FOO WHERE ID IN ( SELECT FOO_ID FROM
BAR ) [doesn't use index]
http://www.feedblog.org/2005/10/what
Hi trying to wtite a trigger to update summary fields in a seperate
table to do this i am planning on using trigger.
problem i have at the moment the update trigger doesnt seem to be
fireing but the insert works.
Trigger
CREATE TRIGGER "setSummary" AFTER INSERT OR UPDATE
ON "parts" FOR EACH RO
Uzo Madujibeya wrote:
Ok,
so I decide to migrate from postgresql 8.0 to 8.0.4 and, as you do, go
to backup my database. On trying to navigate to my bin directory I get
an error message saying the directory doesn't exist. So I check the
pgsql folder and true enough the directory doesn't exis
40 matches
Mail list logo
