Skip to content

issues Search Results · repo:segasai/q3c language:C

Filter by

27 results
 (93 ms)

27 results

insegasai/q3c (press backspace or delete to remove)

segasai/q3c
Error building q3c with newer versions of RHEL / LLVM

On RHEL / AlmaLinux 9.4 with LLVM 17.0.6 we are getting the error below when trying to build q3c. We believe q3c needs to be updated to build with newer versions of LLVM. error: unknown argument: -no-opaque-pointers ...
  • johnny-gossick
  • 1
  • Opened 
    on Sep 25, 2024
  • #40

segasai/q3c
Clarification regarding limitation

As it was mentioned in the limitations, polygon of area larger than 25 degree is not supported , does this translate to angular diameter of 25 degree? I am trying to use this package to query, where I ...
  • Hemanthb1
  • 1
  • Opened 
    on Jul 19, 2024
  • #39

segasai/q3c
If I update the q3c version must we remake the indexes?

Hi, we have recently migrated q3c from version 1.5 to version 2.0 (following the instruction included in the main page). Must we make the indexes from scratch (remove and make them again) or the already ...
  • cosmoJFH
  • 1
  • Opened 
    on May 11, 2023
  • #34

segasai/q3c
support for PARALLEL SAFE

Would it make sense to add PARALLEL SAFE to the SQL definitions for the q3c functions? The Postgresql Documentation states: Functions should be labeled parallel unsafe if they modify any database state, ...
enhancement
help wanted
  • gshennessy
  • 13
  • Opened 
    on Mar 15, 2021
  • #32

segasai/q3c
Getting a 'polygon is too large' error.

Hi, I have the following query using a polygon generated as the boundary of a region (from a FITS header): SELECT * FROM my_catalog WHERE q3c_poly_query(ra, dec, ((255.3121984665786, 18.92312700639222), ...
  • demitri
  • 5
  • Opened 
    on Feb 19, 2021
  • #31

segasai/q3c
Add selectivity estimate?

I m still regularly struggling with abysimal query plans when q3c functions are in queries; disabling seqscans helps a bit of course, but it certainly is not an suboptimal and has unwelcome side effects ...
enhancement
help wanted
  • msdemlei
  • 35
  • Opened 
    on Feb 10, 2021
  • #30

segasai/q3c
Regression test failure with q3c_ang2ipix test

This issue is here to track the problem raised in #28 by @df7cb
  • segasai
  • 2
  • Opened 
    on Oct 12, 2020
  • #29

segasai/q3c
Add instructions for upgrading to README.md?

May I suggesting adding some instructions to README.md regarding how to upgrade an existing installation? It s really simple, but I think it s worth mentioning. ALTER EXTENSION q3c UPDATE; Or to a specific ...
  • esabol
  • 2
  • Opened 
    on Aug 14, 2020
  • #27

segasai/q3c
"make test" should "drop database if exists q3c_test" before "createdb q3c_test"?

Minor thing: I just upgraded our installation from q3c 1.5.0 to 2.0.0, and I mistakenly executed make test before make install. Well, the test failed (because of the proper motion syntax changes in 2.0.0), ...
  • esabol
  • 3
  • Opened 
    on Aug 14, 2020
  • #26

segasai/q3c
pg_repack q3c index

I m dealing with some huge tables for which clustering after creating the q3c index can take several days, during which the tables are locked (I cannot even create indexes for other tables). A non-locking ...
  • albireox
  • 4
  • Opened 
    on Apr 7, 2020
  • #24
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub