[7.0.2] Negative OIDs?
I always thought that an OID was unsigned ...
pgsql=# SELECT oid FROM projects WHERE oid < 0;
oid
-------------
-1727061152
-548634912
-548593248
-886806784
-1001235776
-1196613696
-1198068800
-1228311424
-1344696224
-548591776
-1553984768
-1554041312
-1554147456
-1661653408
-1662100832
-548591104
-1662315872
-1694490400
-1694761376
-1694791904
-1725658848
-548590496
-1725958496
-1726398208
-1727061856
-548589792
-1992983392
-2055459232
-548589376
-2055475456
(30 rows)
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
I always thought that an OID was unsigned ...
It is. But we cheat and use the int4 i/o routines. There are notes in
the sources pointing this out.
- Thomas
Hi all,
I have a problem starting the postgres database.
I am using postgres 7.0.2 on a Redhat Linux 6.2. I had to shutdown my computer
since it was hanging. I have the postgres start command added to the bootup
process. I have rebooted the Linux machine several times and it was starting
postgres correctly. But this time it was saying "Postmaster could not connect to
unix socket 5432" . I checked if any other instance of Postmaster was running by
checking the process ids. There was no second instance running. Also, I tried to
stop and restart postgres using
"/etc/rc.d/init.d/postgres stop" and "/etc/rc.d/init.d/postgres start" commands.
It was saying
"Starting Postres [ ]". If Postgres was really started it will show the process
id within the square brackets. But this time it did not show the process id. If I
try to connect to the database using psql it gives the error message "Postgres
could not be connected to socket 5432".
Please let me know if there is a different way of starting postgres.
Thanks,
Nataraj
The problem is that the "socket" is actually a file. On my system, this
file is "/tmp/.s.PGSQL.5432". Logon as root. Take down PostgreSQL. Then
"rm" that file. PostgreSQL should then start up OK.
On Fri, 1 Sep 2000, Nataraj wrote:
Show quoted text
Hi all,
I have a problem starting the postgres database.
I am using postgres 7.0.2 on a Redhat Linux 6.2. I had to shutdown my computer
since it was hanging. I have the postgres start command added to the bootup
process. I have rebooted the Linux machine several times and it was starting
postgres correctly. But this time it was saying "Postmaster could not connect to
unix socket 5432" . I checked if any other instance of Postmaster was running by
checking the process ids. There was no second instance running. Also, I tried to
stop and restart postgres using
"/etc/rc.d/init.d/postgres stop" and "/etc/rc.d/init.d/postgres start" commands.
It was saying
"Starting Postres [ ]". If Postgres was really started it will show the process
id within the square brackets. But this time it did not show the process id. If I
try to connect to the database using psql it gives the error message "Postgres
could not be connected to socket 5432".Please let me know if there is a different way of starting postgres.
Thanks,
Nataraj
Thanks John.
I will try this when I reconstruct the server from the backup. Just to keep the system
going, I have temporarily reconstructed the entire server from an old Ghost backup. I
will bringback the image of the server which had the postgres startup problem because
I need to recover all the data from the database.
Thanks,
Nataraj
John McKown wrote:
Show quoted text
The problem is that the "socket" is actually a file. On my system, this
file is "/tmp/.s.PGSQL.5432". Logon as root. Take down PostgreSQL. Then
"rm" that file. PostgreSQL should then start up OK.On Fri, 1 Sep 2000, Nataraj wrote:
Hi all,
I have a problem starting the postgres database.
I am using postgres 7.0.2 on a Redhat Linux 6.2. I had to shutdown my computer
since it was hanging. I have the postgres start command added to the bootup
process. I have rebooted the Linux machine several times and it was starting
postgres correctly. But this time it was saying "Postmaster could not connect to
unix socket 5432" . I checked if any other instance of Postmaster was running by
checking the process ids. There was no second instance running. Also, I tried to
stop and restart postgres using
"/etc/rc.d/init.d/postgres stop" and "/etc/rc.d/init.d/postgres start" commands.
It was saying
"Starting Postres [ ]". If Postgres was really started it will show the process
id within the square brackets. But this time it did not show the process id. If I
try to connect to the database using psql it gives the error message "Postgres
could not be connected to socket 5432".Please let me know if there is a different way of starting postgres.
Thanks,
Nataraj
Thomas Lockhart <lockhart@alumni.caltech.edu> writes:
I always thought that an OID was unsigned ...
It is. But we cheat and use the int4 i/o routines. There are notes in
the sources pointing this out.
We also cheat by using the int4 comparison routines, so sort order is
not what it should be ...
regards, tom lane