1. PostgreSQL and pgvector Installation Issues
   The pgvector extension was required for vector-based data retrieval but was missing or incorrectly installed.

Faced errors like "extension vector has no installation script" and "could not open extension control file".

Solution: Manually downloaded and placed the correct vector.control and vector--0.8.0.sql files in the PostgreSQL extension directory.

2. Virtual Environment (venv) Issues
   Initially, all work was done inside the virtual environment, but Git ignored venv/, causing confusion when pushing changes.

Some dependencies had to be reinstalled after switching environments.

Solution: Ensured correct activation of venv and explicitly installed dependencies before deployment.

3. Git & Version Control Challenges
   Git did not recognize modified files even after running git add ..

Encountered issues with .gitignore unintentionally ignoring important files.

Solution: Manually checked tracked files, removed unnecessary ignores, and force-added files where needed.

4. Time Constraints & Debugging
   The hackathon deadline added pressure to fix errors quickly.

Debugging PostgreSQL and system-level issues consumed significant time.

Solution: Prioritized core functionality and systematically resolved errors one by one.

5. Deployment Considerations
   Unsure whether pgvector was necessary locally for submission or if it could be configured only on deployment.

Had to verify .env configurations and database connectivity before deploying.