Catalog

JavaScript is used, and should be enabled to get full functionality.

Looking for catalogs ..

The following problems were encountered in this VizieR run:

**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****db1_relink(0): connection was not opened
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****db1_relink(0): connection was not opened
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_pg,     Status: STDB_ERR 
****Postgres connect error
**** 
**** -- no connection
**** Report from: stdb_pg_conn,     Status: STDB_ERR 
****Couldn't connect with server
**** 
**** -- no connection
**** Report from: stdb_conn_dbms,     Status: STDB_ERR 
****No server is available for connection
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****db1_relink(0): connection was not opened
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1
****Bad db number: -1

If you can't find a solution, report to CDS and insert into your message the following details:

.errorfile=/tmp/VR1763485.err (2026-02-03T13:17:08)
-2
-kw.cat=51401987
-ref=VIZ6981f5541ae89d

elapse time 2


	17280023 J/ApJ/728/23	76368	^(c) 166 166	GALEX UV-bright high-redshift quasars (Worseck+, 2011) ReadMe+ftp 2011ApJ...728...23W	0
	18630144 J/ApJ/863/144	2384	^(c) 0	The ELQS in SDSS footprint. II. North Gal. Cap (Schindler+, 2018) ReadMe+ftp 2018ApJ...863..144S	0
	18710258 J/ApJ/871/258	3316	^(c) 0	ELQS in SDSS. III. The full ELQS quasar catalog (Schindler+, 2019) ReadMe+ftp 2019ApJ...871..258S	0
	18970018 J/ApJ/897/18	349	0	Swift UVOT observation of the radio quasar 3C 273 (Li+, 2020) ReadMe+ftp 2020ApJ...897...18L Objects timeSerie	0
	19740235 J/ApJ/974/235	6210	^(c) 6k 6181	Stripe 82X DR3 catalog: new sp. redshifts (LaMassa+, 2024) ReadMe+ftp 2024ApJ...974..235L	0
	22010010 J/ApJS/201/10	5234	^(c) 1k 1034	SDSS quasar catalog with Swift observations (Wu+, 2012) ReadMe+ftp 2012ApJS..201...10W	0
	22430005 J/ApJS/243/5	3742	^(c) 854 854	The ELQS in the PS1 footprint (PS-ELQS) (Schindler+, 2019) ReadMe+ftp 2019ApJS..243....5S	0
	35840044 J/A+A/584/A44	11353	^(c) 49k 49864	Photometric classification of QSO from RCS-2 (Carrasco+, 2015) ReadMe+ftp 2015A&A...584A..44C	0
	51401987 J/AJ/140/1987	41047	^(c) 19k 19812	SDSS-GALEX QSO catalog (Hutchings+, 2010) ReadMe+ftp 2010AJ....140.1987H	0
ALL				or
			^(c) indicates tables which contain celestial coordinates