[BUGS] Un "sondaggio" e 7 buone azioni...
Salve, sono Emma Bonino, e le propongo un "sondaggio" e 7 iniziative online. Grazie e buona... azione! Quali alleanze per le elezioni politiche ? "SONDAGGIO": http://www.radicali.it/action/sondaggio/ Azioni online: ABORTO E CONTRACCEZIONE Per introdurre in Italia pillola abortiva RU486 http://www.radicali.it/action/ru486/ FREE SOFTWARE Petizione europea contro la brevettabilita' del software http://www.radicali.it/action/freesoft/ LEGALIZZAZIONE DROGHE Sostegno a Pannella e ai radicali sotto processo per disobbedienza civile http://www.radicali.it/action/legalize/ FIRMA DIGITALE E VOTO ELETTRONICO Richiesta al Governo per la legalita' delle elezioni politiche http://www.radicali.it/action/digital/ CONTRO LA TELEVISIONE DI STATO Per abolire la concessione unica radiotelevisiva http://www.radicali.it/action/rai/ CONTRO IL SINDACATO DI STATO Per l'abolizione del sistema di rinnovo automatico dell'iscrizione sindacale http://www.radicali.it/action/sindacato/ LIBERALIZZAZIONE TELECOMUNICAZIONI Per l'abolizione del canone Telecom http://www.radicali.it/action/telecom/ Su questi ed altri temi si confronteranno tra pochi giorni anche le liste delle elezioni radicali online. Per partecipare e votare, clicca qui : http://www.radicali.it/action/register *** PS Questa email e stata inviata nel rispetto della legge sulla privacy; se desidera maggiori informazioni o se intende cancellarsi, puo cliccare qui: http://www.radicali.it/action/privacy/
RE: [BUGS] Fail to restore index tables by pg_dumpall
Dear Tom, Thank you for your reply. It is strangely there was no error message at all when I restore the backup as if everything ran smoothly. I am not sure if the 'initdb --template' command has also cleared away all the system index tables as well. This is because I find out all the system index tables are no longer exists when I run the '\dS' command to list system tables and indexes. I forgot to run this command before I execute the 'initdb --template' command so I am not sure what is the cause. I read from other user's comment from the Internet that one should run this 'initdb' to clear the database. I wonder is that true? I am not sure if I should just drop all the old testing databases in the new machine except template1 database before restoring all the on-line databases onto the new machine. Please advise if possible. Many many thanks. regards, Jessica > -Original Message- > From: Tom Lane [mailto:[EMAIL PROTECTED]] > Sent: 14 November 2000 19:03 > To: Jessica Ord > Cc: [EMAIL PROTECTED] > Subject: Re: [BUGS] Fail to restore index tables by pg_dumpall > > > "Jessica Ord" <[EMAIL PROTECTED]> writes: > > After that, I restored this file onto a newer version of > PostgreSQL 7.0.2 by > > the below command. > > > # psql -e template1 < db.all > > > However, I login to the database and I noticed that all the tables are > > restored properly except all my index tables are missing. > > > I then scrutinized the file generated by the pg_dumpall. For > example, the > > following statement is found in the file but it didn't seem to > create the > > 'status_index' table. > > > CREATE INDEX "status_index" on "ribs_log" using btree ( "status" > > "int4_ops" ); > > The only theory I can come up with is that the restore script failed > before it got as far as the CREATE INDEX commands. Did you look for > any error messages that might've come out of the psql run? > > regards, tom lane >
[BUGS] aktuelle Viruswarnung - BITTE BEACHTEN
> http://www.wetellyou.ch Experten geben Gratis Auskunft! > > Weiterleitungsbitte von T-Kom > - > Thema: aktuelle Viruswarnung - BITTE BEACHTEN > > > > Wir haben soeben eine Viruswarnung der Telekom erhalten > > und bitten um Beachtung: > > > > Bitte weiterleiten an alle Personen, die Sie kennen und > > Internet-Zugang haben. > > > > Vielleicht erhalten Sie per E-Mail einen Bildschirmschoner > > "ZLATKO" in einer Datei "Zlatko.exe". Auf keinen Fall > > > > öffnen > > Sofort löschen! > > Wenn Sie diese Datei entpacken, verlieren Sie alle Daten > > in Ihrem > > Computer, die Festplatte wird komplett gelöscht und die > > Person, die Ihnen > > diese E-mail geschickt hat, erhält Zugang zu Ihrem > > Internet-Namen und dem > > dazugehörigem Passwort. Dieser Virus ist seit Sonntag im > > Umlauf und sehr > > gefährlich! > > > > Mailen Sie an alle Personen aus Ihrem Adressbuch diese > > Warnung. AOL hat > > bestätigt, daß der Virus sehr gefährlich ist und daß noch > > kein > > Antivirenprogramm existiert, daß ihn zerstören konnte. > > Bitte leiten Sie > > diese E-mail weiter an Ihre Kollegen, Bekannte und Freunde. > > > > Mit freundlichen Grüssen > > Deutsche Telekom > > Walther Remitschka > > Disposition, Bezirksbüro Netze 4 > > Technikniederlassung München > > > Mit freundlichen Grüssen > > Jörg Voss > > http://www.wetellyou.ch Experten geben Gratis Auskunft! Stop info mails: http://netad24.com/cgi-bin/unsubscribe?[EMAIL PROTECTED]
Re: [BUGS] Fail to restore index tables by pg_dumpall
"Jessica Ord" <[EMAIL PROTECTED]> writes: > I am not sure if the 'initdb --template' command has also cleared away all > the system index tables as well. initdb --template? Why are you using that? I think that's a poorly debugged (to put it kindly) feature. I'd recommend staying away from it. Assuming that you are careful not to put any user data into template1, there is no reason ever to reinitialize template1 after the initial initdb. At this point I think you may have to do a full initdb to get back into a good state. If you have backups of everything, that seems like the way to go rather than trying to dig your way out of the hole bit by bit. regards, tom lane
Re: [BUGS] no meaningful way to determine fe or be version?
You can do a 'SELECT version()' to get a version string from the backend. > Paul M. Aoki ([EMAIL PROTECTED]) reports a bug with a severity of 3 > The lower the number the more severe it is. > > Short Description > no meaningful way to determine fe or be version? > > Long Description > both the odbc and jdbc drivers seem to hardcode the database version, e.g., >org/postgresql/jdbc2/DatabaseMetaData.java always returns "6.5.2" when you call >getDatabaseProductVersion(). > > it would be nice if the metadata routines were actually tied to something returned >from the backend. > > Sample Code > > > No file was uploaded with this report > > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026
[BUGS] FOREIGN KEY check needs UPDATE permission
Viljar Tulit ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
FOREIGN KEY check needs UPDATE permission
Long Description
Lets you have 2 table. First SELECT only. Second with ALL privileges. And from second,
there is REFERENCE to first.
Now if you INSERT something to second, it fails with no permission error in first,
SELECT only table.
FOREIGN KEY check needs UPDATE permission for table, where key lives.
Sample Code
Exampel database:
CREATE USER yks NOCREATEDB NOCREATEUSER;
CREATE USER kaks NOCREATEDB NOCREATEUSER;
CREATE DATABASE bug;
\c bug
/* create table, where kaks is RO access privileges
and yks is all privileges */
CREATE SEQUENCE xxx_seq;
GRANT SELECT ON xxx_seq TO kaks;
GRANT SELECT,UPDATE ON xxx_seq TO yks;
CREATE TABLE xxx(
nimi text,
id int4 DEFAULT nextval('xxx_seq') NOT NULL,
PRIMARY KEY(id));
GRANT SELECT ON xxx TO kaks;
GRANT ALL ON xxx TO yks;
/* create table, where yks is all privileges */
CREATE SEQUENCE yyy_seq;
GRANT SELECT,UPDATE ON yyy_seq TO kaks;
CREATE TABLE yyy(
andmed text,
tekitas int4 REFERENCES xxx(id),
id int4 DEFAULT nextval('yyy_seq') NOT NULL,
PRIMARY KEY(id));
GRANT ALL ON yyy TO kaks;
now bug:Welcome to psql, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help on internal slash commands
\g or terminate with semicolon to execute query
\q to quit
psql -Upostgres bug
bug=# \z
Access permissions for database "bug"
Relation |Access permissions
--+---
xxx | {"=","yks=arwR","kaks=r"}
xxx_seq | {"=","yks=rw","kaks=r"}
yyy | {"=","kaks=arwR"}
yyy_seq | {"=","kaks=rw"}
(4 rows)
bug=# \c - yks
You are now connected as new user yks.
bug=> INSERT INTO xxx (nimi) values ('viljar');
INSERT 31552 1
bug=> \c - kaks
You are now connected as new user kaks.
bug=> INSERT INTO yyy (andmed,tekitas) values ('buug',1);
ERROR: xxx: Permission denied.
No file was uploaded with this report
